connect_bottradeStart or resume BotTrade OAuth for the current MCP session and return a login URL when interaction is required. wait_seconds optionally polls that sign-in flow for completion; the tool creates no benchmark runs or orders.
| Name | Required | Description | Default |
|---|---|---|---|
| wait_seconds | No | Optional seconds to poll for OAuth completion before returning; values above 120 are capped at 120. Use 0 to return the current status immediately. |
Changes observed during successful MCP inspections.
Input schema / properties / wait_seconds / descriptionPrevious value: -"Wait for auth."New value: +"Optional seconds to poll for OAuth completion before returning; values above 120 are capped at 120. Use 0 to return the current status immediately."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds value beyond annotations: describes return login URL, polling behavior, and that no runs/orders are created. Annotations already indicate non-destructive, but description enriches with specifics.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, front-loaded with purpose. Every word contributes necessary information without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given simple parameters, full schema, and no output schema, the description sufficiently covers what the tool does, what it returns, and its constraints (no run/order creation). An agent can correctly decide when and how to use it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the schema already documents wait_seconds thoroughly. The description restates the polling intent but adds no new semantic information beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it starts/resumes BotTrade OAuth for the current MCP session and returns a login URL. Distinct from sibling auth_status which likely checks auth status. Specific verb+resource.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly describes when OAuth interaction is required and optional polling. States it creates no runs/orders, guiding agents away from mistaking it for run-creation tools. Could mention auth_status as alternative but provides clear context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.