Financial Modeling Prep MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only mentions it retrieves 'real-time' data without specifying rate limits, authentication requirements, data freshness guarantees, or error conditions. It doesn't describe what 'other relevant data' includes or the response format.

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?

The description is efficiently structured in two sentences: first stating the core function and API source, second detailing the data types and context. No wasted words, though it could be slightly more front-loaded with the multi-stock distinction.

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?

For a data retrieval tool with no annotations and no output schema, the description is incomplete. It doesn't specify response format, pagination, error handling, or what 'other relevant data' entails. The absence of behavioral details and output information leaves significant gaps for agent understanding.

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 description coverage is 100% with the single 'symbols' parameter well-documented as 'Comma-separated list of stock symbols'. The description adds no additional parameter semantics beyond what the schema already provides, so baseline 3 is appropriate.

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?

The description clearly states the tool's purpose: 'Retrieve real-time aftermarket quotes for multiple stocks' with the FMP Batch Aftermarket Quote API, specifying it provides bid/ask prices, volume, and other data during post-market trading. It distinguishes from sibling 'getAftermarketQuote' by handling multiple stocks, but doesn't explicitly mention this distinction.

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?

The description implies usage during post-market trading and for multiple stocks, but doesn't provide explicit guidance on when to use this versus alternatives like 'getBatchQuotes' or 'getAftermarketQuote'. No when-not-to-use scenarios or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.