Skip to main content
Glama

FinanceQuery

Forex News

get_forex_news
Read-onlyIdempotent

Get market-wide forex 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_forex_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.8/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 the one trait annotations cannot express: results come from FMP only and require FMP_API_KEY, which is direct auth/dependency context. It stops short of describing return shape or pagination behavior.

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 sentence with zero filler, front-loading the resource and immediately qualifying scope and dependency. Nothing is redundant or padding.

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

Completeness4/5

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

For a read-only news fetch with all-optional, fully documented parameters and a rich annotation set, the description covers the essential operational fact (provider/API key). It is slightly thin on pagination expectations and on what 'market-wide' excludes, but the schema carries the parameter burden.

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%, with count, limit, cursor and fields each documented including defaults and the cursor's origin field. The description adds no meaning beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ('Get market-wide forex news') and scopes it to the forex asset class, which separates it from generic get_news and from get_crypto_news in the sibling list. It does not name an alternative tool, so it falls short of the top mark.

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 by the name and the 'market-wide' qualifier; there is no explicit when-to-use, when-not, or routing to get_news/get_crypto_news for other asset classes. The provider prerequisite is useful but is a precondition, not selection 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.