refactor!: trim mcp tools to core three

[sommio]

What

Trim MCP tool surface from 8 to 3: keep analyze_video, analyze_image, check_endpoint_status.

Remove:

• summarize_video — prompt sugar over analyze_video
• extract_video_text — prompt sugar over analyze_video
• video_qa — identical to analyze_video + question
• compare_video_frames — prompt sugar over analyze_video
• list_capabilities — static info the client model does not need

Why

Only analyze_video and analyze_image are used in practice. The four video tools were fixed-prompt wrappers; the model client can pass the same prompt directly. Fewer tools = less tool-list noise, less surface to maintain. check_endpoint_status kept as a zero-token config/key diagnostic.

src/prompts.ts deleted — all exports served the removed tools, zero references remain.

Breaking change

MCP clients referencing any of the 5 removed tool names will break. Migrate to analyze_video / analyze_image with an explicit prompt.

Verification

• npm run typecheck ✓
• npm run lint (--max-warnings 0) ✓
• npm run format:check ✓
• npm test — 61 passed, 3 skipped (live) ✓
• npm run coverage — 98.42% (threshold 85%) ✓
• npm run build ✓

Files

• src/server.ts — remove 5 tool registrations + clean imports
• src/prompts.ts — deleted
• test/tools.test.ts — tool count 8→3, drop 4 tests, URL passthrough test uses analyze_video
• README.md — tools table 8→3
• AGENTS.md — tool list 8→3

---

Do not merge — awaiting review.

[coderabbitai]

Warning

Review limit reached

@sommio, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 27 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: QUIET

Plan: Pro Plus

Run ID: bd4650b9-9de2-426c-ab5e-26da598595f8

📥 Commits

Reviewing files that changed from the base of the PR and between e45d96d and d5febc4.

📒 Files selected for processing (5)

• AGENTS.md
• README.md
• src/prompts.ts
• src/server.ts
• test/tools.test.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}