Skip to main content
Glama

FinanceQuery

Stock and Market News

get_news
Read-onlyIdempotent

Get recent news. If a symbol is provided, returns news for that stock; otherwise returns general market news.

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

Input Schema

NameRequiredDescriptionDefault
langNoTarget language for translated text fields (BCP 47, e.g. "ja", "zh-Hant"); English or omitted = no translation
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
symbolNoStock ticker symbol (optional; omit for general market news)

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, non-destructive and open-world, so safety is covered. The description adds only that scope is symbol-dependent and that results are 'recent' — it says nothing about pagination via cursor, default page size, or translation behavior, all of which the agent must discover from the schema.

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?

Two short sentences, front-loaded with the action and immediately followed by the branching rule. There is no filler, hedging, or repetition.

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?

With five optional parameters and full schema coverage, the description needs only to explain the tool's purpose and mode selection, which it does. The remaining gap is that no output schema exists and the description never indicates what an article record contains, though 'news' is a reasonably self-evident return type.

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 lang, limit, cursor and fields are fully documented in the schema and the baseline is 3. The description's only parameter-relevant content restates the symbol parameter's effect, adding no format, default, or interaction detail beyond structured data.

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 gives a specific verb and resource ('Get recent news') and states the two operating modes: per-symbol news versus general market news. It does not name any sibling, so an agent must infer the boundary with get_crypto_news and get_forex_news from names alone.

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 'if a symbol is provided... otherwise...' clause tells the agent how to choose between the two modes of this tool, which is real guidance. It stops short of saying when to prefer this over the crypto or forex news siblings, so usage is only implied at the category boundary.

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.