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

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

searchCryptoNews

Read-onlyIdempotent

Search cryptocurrency news by coin name or symbol to retrieve relevant articles for specific tokens, with optional date-range and result-limit filters.

Instructions

Search for cryptocurrency news using the FMP Search Crypto News API. Retrieve news related to specific coins or tokens by entering their name or symbol.

Input Schema

NameRequiredDescriptionDefault
toNoEnd date (YYYY-MM-DD)
pageNoPage number (default: 0)
limitNoLimit on number of results (default: 20, max: 250)
symbolsYesComma-separated list of cryptocurrency symbols
from_dateNoStart 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": "Start date (YYYY-MM-DD)",
-  "type": "string"
-}
    • addedInput schema / properties / from_date
      Added value: +{
+  "description": "Start date (YYYY-MM-DD)",
+  "type": "string"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and idempotency are covered structurally. The description adds only that results are tied to a supplied coin name/symbol; it says nothing about pagination defaults, result caps, date-range filtering behavior, or that results come from an external live news source beyond the openWorld annotation.

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

Conciseness4/5

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

Two short sentences, front-loaded with the core action, with no filler. The second sentence is largely a restatement of the first and could be merged, but nothing is wasted or buried.

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

Completeness3/5

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

For a five-parameter read-only search tool with no output schema, the description covers the essential purpose but omits the date-range and pagination dimensions that materially shape results. It also leaves the name-vs-symbol ambiguity unresolved, so an agent must read the schema to call it correctly.

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 the five parameters (symbols, from_date, to, page, limit) are already fully documented in the schema, establishing a baseline of 3. The description mentions only the symbol input and even loosely says 'name or symbol' while the schema requires a comma-separated symbol list, adding no real meaning beyond the schema.

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

Purpose4/5

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

The description states a specific verb and resource ('Search for cryptocurrency news') and names the underlying FMP endpoint, so the intent is unambiguous. It does not distinguish itself from the closely related sibling getCryptoNews, which an agent would have to disambiguate on its own.

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

Usage Guidelines3/5

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

Usage is only implied: 'Retrieve news related to specific coins or tokens by entering their name or symbol' suggests symbol-targeted news retrieval. There is no explicit statement of when to choose this over getCryptoNews or searchStockNews/searchForexNews, and no prerequisites or exclusions are given.

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