Skip to main content
Glama

Leeway Financial Data

news

news
Read-only

News for companies, stocks, and currencies. Pass s as SYMBOL.EXCHANGE when you want one instrument. from and to are YYYY-MM-DD. An empty list means no articles in that window; widen from and to before concluding there is no coverage.

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": "news"
  }
}

Input Schema

NameRequiredDescriptionDefault
sNoFormat: Code.Exchange. The code for which the news are queried .
toNoYYYY-MM-DD. The end date.
fromNoFormat: YYYY-MM-DD. The start date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish that this is a safe read (readOnlyHint=true, openWorldHint=false), so the description's main contribution is the note that an empty list means no articles in that window and that from/to should be widened before concluding there is no coverage. That is genuinely useful interpretive context that prevents a wrong negative conclusion. It still omits result limits, ordering, and 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.

Conciseness4/5

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

Three short sentences: purpose first, then parameter formats, then the empty-result caveat. Nothing is padded, and the most decision-relevant caveat is placed where it will be read. Minor redundancy with the schema on date formats keeps it from a 5.

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?

The empty-window warning is a meaningful addition, but with zero required parameters the description never states what the default scope is when only some or none of s/from/to are supplied. No output schema exists, so sorting, result caps, and article shape are undocumented. Adequate for a simple three-param read, but with clear gaps.

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 the schema already documents all three parameters including the Code.Exchange and YYYY-MM-DD formats. The description restates those same formats ('s as SYMBOL.EXCHANGE', 'from and to are YYYY-MM-DD') without adding meaning beyond the schema, which is the baseline-3 case. Note that the description's 'SYMBOL.EXCHANGE' framing slightly diverges from the schema's 'Code.Exchange' wording.

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 first sentence names the resource and its coverage domain (companies, stocks, currencies), making it distinguishable from siblings like sentiment or events. The retrieval verb is only implied by the noun 'News', so it is clear but not verb-precise.

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 description tells the agent to pass 's' when targeting a single instrument, which implicitly distinguishes instrument-scoped from broad queries. It gives no guidance on when to use this versus related siblings such as sentiment or events, and does not explain what happens when all three optional parameters are omitted.

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.

Resources