Skip to main content
Glama
Sign In
Financial Modeling Prep MCP Server

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getFundDisclosureDates

Read-onlyIdempotent

Retrieve mutual fund and ETF disclosure details by filing date to track regulatory filings and stay current with required updates.

Instructions

Retrieve detailed disclosures for mutual funds and ETFs based on filing dates with the FMP Fund & ETF Disclosures by Date API. Stay current with the latest filings and track regulatory updates effectively.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "getFundDisclosureDates"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoOptional CIK number
symbolYesFund symbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.9.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety and idempotency profile is covered without help from the description. The description adds essentially nothing beyond that: no indication of the shape of a 'disclosure', no pagination or result-size behavior, and no note on what happens when a symbol has no filings. With annotations carrying the main burden, this lands at a 3 rather than lower.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the useful clause, but the second sentence is filler that would not change an agent's decision. Not bloated, but not every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no output schema, the description still leaves an agent unsure what a 'disclosure' record contains, how many are returned, or how symbol and cik interact. The absence of output schema means the description should have sketched the payload, and it does not.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so 'symbol' and 'cik' are already documented as structured fields, and the high-coverage baseline would be a 3. But the description says results are keyed 'based on filing dates' when no date parameter exists in the schema, which actively points an agent toward an input it cannot supply and adds no meaning about symbol vs. cik precedence.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Retrieve detailed disclosures for mutual funds and ETFs') and a namespace (FMP Fund & ETF Disclosures by Date API), which is clearer than a tautology. However, among nearby siblings like getFundDisclosure, searchFundDisclosures, getDisclosure, and getESGDisclosures, nothing distinguishes this tool, and the stated 'filing dates' orientation conflicts with a schema whose only required input is a fund symbol.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus getFundDisclosure or searchFundDisclosures, and no stated preconditions. The second sentence ('Stay current with the latest filings and track regulatory updates effectively') is promotional framing rather than an actionable when-to-use rule.

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

Deploy Server

Other Tools