docs: MCP tool catalog rewrite#170
Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
2 issues found across 1 file
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="mcp.mdx">
<violation number="1" location="mcp.mdx:39">
P2: Custom agent: **Enforce Clear Code Style and Maintainability Practices**
`mcp.mdx` exceeds the custom maximum file size limit (161 lines vs required under 100), reducing readability and maintainability per Rule 2.</violation>
<violation number="2" location="mcp.mdx:157">
P2: Custom agent: **Documentation and Naming Conventions for Maintainable Code**
Public API docs removed concrete response/error behavior details and replaced them with generic schema guidance, reducing clarity on error transitions required by the rule.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| See [`POST /api/sandboxes`](/api-reference/sandboxes/create) for the equivalent REST endpoint. | ||
|
|
||
| **Input schema:** | ||
| Each tool's input schema is published over the MCP protocol, so your agent gets typed parameter help automatically. |
There was a problem hiding this comment.
P2: Custom agent: Documentation and Naming Conventions for Maintainable Code
Public API docs removed concrete response/error behavior details and replaced them with generic schema guidance, reducing clarity on error transitions required by the rule.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At mcp.mdx, line 157:
<comment>Public API docs removed concrete response/error behavior details and replaced them with generic schema guidance, reducing clarity on error transitions required by the rule.</comment>
<file context>
@@ -1,78 +1,161 @@
-See [`POST /api/sandboxes`](/api-reference/sandboxes/create) for the equivalent REST endpoint.
-
-**Input schema:**
+Each tool's input schema is published over the MCP protocol, so your agent gets typed parameter help automatically.
-| Parameter | Type | Required | Description |
</file context>
| @@ -1,78 +1,161 @@ | |||
| --- | |||
There was a problem hiding this comment.
P2: Custom agent: Enforce Clear Code Style and Maintainability Practices
mcp.mdx exceeds the custom maximum file size limit (161 lines vs required under 100), reducing readability and maintainability per Rule 2.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At mcp.mdx, line 39:
<comment>`mcp.mdx` exceeds the custom maximum file size limit (161 lines vs required under 100), reducing readability and maintainability per Rule 2.</comment>
<file context>
@@ -1,78 +1,161 @@
+---
-**Response fields:**
+## Tool catalog
-| Field | Type | Description |
</file context>
Brings mcp.mdx in line with what's actually registered in the production MCP server (api/lib/mcp/tools/). The previous page documented 2 tools; the actual server registers 43 across 11 domains. Replaces the previous 2-tool description with a real tool catalog grouped by activity: - Artists (4 tools) - Spotify (4) - Catalog (3) - YouTube (5) - Chats (2) - Tasks (5) - Content — image, video, - Pulses (2) audio (8) - Sandbox (1) - Research (4) - Utilities (3) Tool names and descriptions extracted directly from the register*Tool.ts source files for accuracy. Also fixes: - Removes the fictional `run_sandbox_command` tool (never existed in the registered tool set). - Drops the "Beta" framing — 43 working tools is just under- marketed production, not beta. - Trims the overpromise in the opening line to match the actual capability surface. Made-with: Cursor
recoupableorg
force-pushed
the
feat/docs-mcp
branch
from
f46604f to
edc3932
Compare
2 participants
Summary
Surfaces the 43 production MCP tools that were previously hidden behind a 2-tool description. The MCP server has been silently growing and its docs hadn't kept up.
Why this matters
The previous `mcp.mdx` listed only `prompt_sandbox` and a fictional `run_sandbox_command`. The actual production server (`api/lib/mcp/tools/`) registers 43 tools across 11 domains — Spotify search, YouTube revenue, image generation, deep research, transcription, and more. Agents reading the old docs would never discover most of the platform's capability through MCP.
What changed
Replaced the previous "Available tools" section with a "Tool catalog" organized by activity:
Tool names and descriptions were extracted directly from the `register*Tool.ts` source files. Removed the fictional `run_sandbox_command` and the misleading "Beta" framing.
Stack
PR 3 of 7. Replaces #145.
Test plan
Made with Cursor