Skip to main content
Glama

FinanceQuery

Financial News Feeds

get_feeds
Read-onlyIdempotent

Fetch RSS/Atom news from financial publishers (Bloomberg, WSJ, MarketWatch, FT, SEC, etc.).

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_feeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum entries 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
sourcesNoComma-separated feed sources: federal-reserve|sec|marketwatch|cnbc|bloomberg|ft|nyt| guardian|investing|bea|ecb|cfpb|wsj|fortune|businesswire|coindesk|cointelegraph| techcrunch|hackernews|oilprice|calculatedrisk|scmp|nikkei|boe|venturebeat|yc| economist|financialpost|ftlex|ritholtz (default: marketwatch, bloomberg, wsj, fortune)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds nothing beyond annotations — no mention of pagination behavior (despite a cursor param), freshness/latency, rate limits, or what happens with an invalid source string.

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 that front-loads the verb and resource with zero filler. The parenthetical source examples are the only added content and are directly relevant.

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 feed fetcher with rich annotations and a fully documented schema, the definition is close to sufficient. The remaining gap is routing: a crowded news-oriented sibling set means the description should say how this differs from get_news and the crypto/forex variants.

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 coverage is 100%, so all four parameters are documented in structured form, including the full sources enum and the default set. The description's publisher examples merely echo the schema rather than adding syntax, defaults, or interaction rules, so the baseline 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 ('Fetch') and resource ('RSS/Atom news from financial publishers') and names representative sources. It does not distinguish itself from close siblings like get_news, get_crypto_news, or get_forex_news, so an agent must infer the split from the word 'financial publishers'.

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: the publisher list and 'financial' framing suggest general market news rather than crypto/forex-specific feeds, but the description never says when to pick this over get_news or the vertical feeds, nor any exclusion.

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.