Skip to main content
Glama

Bullion Trading: Gold & Silver

Get market news

get_market_news
Read-onlyIdempotent

The precious-metals market news summary for a day (default the latest): market mood, headline, a short summary, key points, source headlines with links, and the weekly recap link. Use when the user asks for the day's precious-metals market news summary. Read-only; news summary, not advice.

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

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD; default the latest day

Output Schema

NameRequiredDescriptionDefault
dateYes
moodYes
notesYes
headlinesYes
price_timeYes
source_urlYes
summary_textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and non-destructive, so 'read-only' mostly restates structured data. The one genuinely additive piece is the 'news summary, not advice' framing, which tells the agent how to present the content, plus the default-to-latest behavior. No further behavioral detail (freshness, coverage gaps) is offered.

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?

Two sentences, front-loaded with what the tool returns and followed by the trigger condition and disclaimer. The content enumeration is somewhat list-like but each item tells the agent what to expect in the payload; nothing is redundant filler.

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?

An output schema exists, so the description need not explain return values, yet it summarizes them helpfully anyway. For a zero-required-parameter read tool with full schema coverage and rich annotations, the definition gives an agent everything needed to select and call it; only sibling-level routing is left implicit.

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% and the single `date` parameter already documents the YYYY-MM-DD format and latest-day default. The description only echoes the default behavior without adding validation or fallback details, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('precious-metals market news summary for a day') and enumerates exactly what the summary contains (mood, headline, summary, key points, source headlines with links, weekly recap link). Neither the name nor any sibling (find_bullion, get_spot_prices, get_premiums) covers this news-summary niche, so an agent can distinguish it immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use when the user asks for the day's precious-metals market news summary,' which is a concrete trigger condition. It does not name exclusions or alternatives (e.g., price history vs. news), so the routing guidance is clear but not exhaustive.

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