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 of behavioral disclosure. It states the tool 'provides access to detailed cash flow reports' and 'enables users to retrieve bulk cash flow statement data,' which implies a read-only operation. However, it lacks critical behavioral details such as rate limits, authentication requirements, data freshness, pagination for large datasets, error handling, or the format of returned data. For a bulk retrieval tool with no annotation coverage, this is a significant gap.

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 concise and well-structured in two sentences: the first introduces the API's purpose, and the second explains its utility. There's no redundant information, and it's front-loaded with the core function. However, it could be slightly more direct by starting with the action (e.g., 'Retrieve bulk cash flow statements...'), but overall it's efficient.

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 complexity of a bulk financial data tool with no annotations and no output schema, the description is incomplete. It covers the basic purpose but lacks essential context: no details on output format (e.g., JSON, CSV), data structure, handling of multiple companies, error cases, or performance considerations. For a tool that likely returns large datasets, this omission reduces its usefulness for an AI agent.

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?

The input schema has 100% description coverage, with clear documentation for 'year' and 'period' parameters. The description adds no specific parameter semantics beyond what the schema provides—it doesn't explain how these parameters filter the bulk data, their interaction, or any constraints (e.g., valid year ranges). Given the high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 bulk cash flow statement data' for 'a wide range of companies' to 'analyze companies’ operating, investing, and financing activities over time.' This specifies the verb (retrieve), resource (cash flow statement data), and scope (bulk, multiple companies). However, it doesn't explicitly differentiate from sibling tools like getCashFlowStatement or getCashFlowStatementGrowth, which appear to handle individual or growth-focused queries.

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 provides no guidance on when to use this tool versus alternatives. It mentions analyzing cash flow activities but doesn't specify scenarios where bulk retrieval is preferred over single-company tools (e.g., getCashFlowStatement) or other bulk financial tools (e.g., getBalanceSheetStatementsBulk). There's no mention of prerequisites, limitations, or typical use cases beyond general analysis.

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