Financial Modeling Prep MCP Server

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

No annotations are provided, so the description carries full burden. It mentions the API source (FMP Stock News Feed API) and data fields, but lacks critical behavioral details: pagination behavior (implied by 'page' parameter but not explained), rate limits, authentication requirements, data freshness, or error handling.

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 sentences efficiently convey the tool's purpose and data scope without redundancy. However, the second sentence could be more front-loaded with key constraints (e.g., date range required).

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 4-parameter tool with no annotations and no output schema, the description is insufficient. It doesn't explain the return format structure, pagination mechanics, or important constraints like the 'limit' maximum (250), leaving 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%, so parameters are fully documented in the schema. The description adds no parameter-specific information beyond implying date filtering through 'latest' and 'most recent articles', which aligns with the 'from'/'to' parameters but doesn't provide additional semantic context.

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: 'Stay informed with the latest stock market news' and specifies the data returned (headlines, snippets, URLs, ticker symbols). It distinguishes from siblings like 'searchStockNews' by focusing on a feed rather than search, but doesn't explicitly contrast them.

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?

No guidance is provided on when to use this tool versus alternatives like 'searchStockNews', 'getCryptoNews', or 'getGeneralNews'. The description mentions 'latest' but doesn't clarify if this is for real-time updates or historical browsing.

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