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

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getCOTReports

Read-onlyIdempotent

Retrieve Commitment of Traders (COT) reports for a commodity symbol, with optional date filters, to analyze long and short positions and assess market sentiment.

Instructions

Access comprehensive Commitment of Traders (COT) reports with the FMP COT Report API. This API provides detailed information about long and short positions across various sectors, helping you assess market sentiment and track positions in commodities, indices, and financial instruments.

Input Schema

NameRequiredDescriptionDefault
toNoOptional end date (YYYY-MM-DD)
symbolYesCommodity symbol
from_dateNoOptional start date (YYYY-MM-DD)

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. Changed2 schema fields changedv2.6.10
    • removedInput schema / properties / from
      Removed value: -{
-  "description": "Optional start date (YYYY-MM-DD)",
-  "type": "string"
-}
    • addedInput schema / properties / from_date
      Added value: +{
+  "description": "Optional start date (YYYY-MM-DD)",
+  "type": "string"
+}
  3. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds essentially no behavior beyond that: nothing about how the date range is interpreted, defaults when from_date/to are omitted, result volume, ordering, or what a COT record looks like.

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 on the resource, but the second sentence is marketing copy about sectors and market sentiment that does little to help an agent invoke the tool correctly. It is short, yet some of it does not earn 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 tool with a required symbol and an optional date window, the description never explains what the date range does or what happens with no dates, and there is no output schema to fall back on. The picture an agent gets is incomplete relative to a three-parameter historical-report tool.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters (symbol, from_date, to) are already documented with types and date format. The description adds no meaning beyond the schema and never even mentions the required symbol, so the baseline 3 applies.

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 verb is generic ("Access") and the sentence is framed around the upstream API rather than the tool, but the resource — Commitment of Traders reports with long/short positioning by sector — is identifiable. It does not distinguish this tool from the close siblings getCOTAnalysis and getCOTList, which is a real ambiguity given the crowded namespace.

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 when-to-use guidance, no mention of prerequisites, and no reference to alternatives. The description notes the data can help "assess market sentiment," which gestures at a use case but gives no rule for choosing getCOTReports over getCOTAnalysis or getCOTList.

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