Skip to main content
Glama

FinanceQuery

Crypto News

get_crypto_news
Read-onlyIdempotent

Get market-wide crypto news (currently FMP only, requires FMP_API_KEY).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_crypto_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoOverall cap on articles fetched (default: 20)
limitNoMaximum articles per page; omitted = curated default (25)
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: data is currently sourced from FMP only and a FMP_API_KEY is required, which tells the agent about a likely failure mode. It says nothing about result volume or freshness, but the auth caveat is the material addition.

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

Conciseness5/5

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

A single short sentence with the resource and provider constraint front-loaded; nothing is redundant or padded.

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 read-only, zero-required-parameter news fetch this is close to adequate, and the cursor/fields semantics live in the schema. However, with no output schema there is no description of what an article record contains or how pagination behaves across pages, leaving the return shape to inference.

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 four parameters (count, limit, cursor, fields) are already self-documenting. The description adds no parameter meaning beyond the schema, which is the expected baseline here.

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?

Specific verb+resource: 'Get market-wide crypto news' states both the action and the scope ('market-wide'), which implicitly distinguishes it from per-coin or general news retrieval. It does not name a sibling tool, so differentiation is inferred rather than explicit.

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?

The word 'market-wide' implies the usage context (broad crypto news rather than asset-specific news), but the description never states when to prefer this over get_news or a coin-level feed, nor any exclusions. The FMP provider note gives a prerequisite but not routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.