Skip to main content
Glama

Get Stock Token quote

get_stock_quote
Read-only

Fetch a stock token quote by ticker, including Chainlink oracle price, Uniswap DEX mid price, premium/discount, and ERC-8056 multiplier for underlying share price.

Instructions

Price a Stock Token by ticker: the Chainlink oracle price, the on-chain Uniswap DEX mid price, the premium/discount between them, and the ERC-8056 multiplier (so you also get the underlying share price).

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

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker, e.g. "AAPL" or "TSLA" (case-insensitive).
maxAgeSecondsNoReject the Chainlink answer if older than this (default 3 days; 24/5 feeds).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / maxAgeSeconds / maximum
      Added value: +9007199254740991
  2. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior. The description adds meaningful context by identifying the Chainlink oracle and Uniswap DEX sources, the premium/discount calculation, and the ERC-8056 multiplier that yields the underlying share price; it does not discuss errors or rate limits, but that is a modest gap for a quote read.

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?

One front-loaded sentence: purpose first, then the returned values, with a useful parenthetical. No filler or repeated title language.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description's enumeration of oracle price, DEX mid, premium/discount, and multiplier/underlying share price is important and sufficient for the return shape. The optional maxAgeSeconds behavior is left to the schema, which is reasonable given full schema coverage.

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?

With 100% schema coverage, both symbol and maxAgeSeconds are documented in the schema. The description only reinforces ticker usage and does not explain maxAgeSeconds or add syntax beyond the schema, so baseline 3 is appropriate.

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?

The description gives a specific verb ('Price') and resource ('Stock Token by ticker') and enumerates the returned pricing components. That level of specificity separates it from listing/searching tools even without naming a sibling.

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?

It implies the tool is for retrieving a single ticker's quote, but gives no explicit when-to-use/when-not guidance or named alternative among list_stock_tokens, search_token, or get_coin. Routing is therefore left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.