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 the full burden. It mentions the API source but does not disclose behavioral traits such as whether it's a read-only operation, potential rate limits, authentication needs, or response format. The description is minimal and lacks essential operational context.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary details. It is front-loaded with the main action and resource, though it could be slightly more structured to highlight key features.

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 the tool has no annotations and no output schema, the description is insufficient. It lacks details on behavior, response format, error handling, or practical usage scenarios. For a tool with parameters and no structured support, the description should provide more comprehensive guidance.

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 the schema already documents both parameters ('industryTitle' and 'sicCode'). The description does not add any additional meaning or examples beyond what the schema provides, such as how filtering works or typical use cases for these parameters.

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 verb 'Retrieve' and resource 'comprehensive list of industry classifications', specifying it includes SIC codes and industry titles via the FMP API. It distinguishes from siblings like 'getAllIndustryClassification' by focusing on a filtered list rather than all classifications, though the distinction could be more explicit.

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 for retrieving industry classifications, but does not explicitly state when to use this tool versus alternatives like 'getAllIndustryClassification' or 'searchIndustryClassification'. It provides some context by mentioning the API source, but lacks clear guidance on use cases or exclusions.

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