Skip to main content
Glama

stock_quote

Live stock/ETF/index/FX quote: price, change, day range, volume, 52-week range. $0.01 USDC on Base (x402).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "stock_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does deliver the single most important behavioral fact: this is a paid endpoint settled in $0.01 USDC on Base via x402. It also discloses the return fields and that data is 'Live'. It omits how payment is authorized, whether quotes are real-time or delayed, and behavior when markets are closed.

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 dense clauses, front-loaded with what the tool returns and ending with the cost/rail. Every fragment earns its place with no filler.

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?

For a one-parameter read tool with no output schema, listing the returned fields substitutes well for a return spec, and the payment disclosure is valuable. However, without annotations or an output schema, the missing symbol-format rules and payment/auth mechanics leave real gaps an agent would hit at call time.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

One required parameter with 0% schema coverage, so the description must compensate and it largely does not. It never shows a symbol format example and gives no guidance for the asset classes it advertises — ticker vs. FX pair notation (e.g. EUR/USD vs EURUSD) vs. index symbols remain ambiguous.

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 ('Live ... quote') plus the exact asset classes covered (stock/ETF/index/FX) and the fields returned (price, change, day range, volume, 52-week range). This implicitly separates it from eth_price and weather, though it never names an alternative explicitly.

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 gives no explicit when-to-use or when-not-to-use guidance and no prerequisites beyond the price line. The $0.01 USDC / x402 note does hint that this is a paid call, which is decision-relevant, but the agent must infer the conditions under which it should be preferred over siblings.

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