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 states 'Retrieve' implying a read operation, but lacks details on permissions, rate limits, data freshness, or response format. For a tool with no annotation coverage, this leaves significant behavioral gaps unaddressed.

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 front-loads the core purpose and lists data types. It avoids redundancy but could be slightly more structured by separating usage context from data details.

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 no annotations, no output schema, and a tool that retrieves detailed profiles, the description is incomplete. It lacks information on response structure, error handling, authentication needs, or data scope limitations, making it inadequate for full contextual 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 both parameters ('symbol', 'cik') clearly documented in the schema. The description adds no additional parameter semantics beyond implying these are used to identify companies for SEC profiles, which is already inferred from the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 detailed company profiles' with specific data types (business descriptions, executive details, contact information, financial data) and identifies the API source (FMP SEC Company Full Profile API). It distinguishes from siblings like 'getCompanyProfile' by specifying SEC focus and full profile scope, though not explicitly contrasting with all similar tools.

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 explicit guidance on when to use this tool versus alternatives is provided. The description mentions the API source but doesn't specify scenarios, prerequisites, or exclusions. Siblings like 'getCompanyProfile' and 'getCompanyProfileByCIK' exist without clear differentiation in usage context.

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