Skip to main content
Glama

Valeur Intrinsèque

get_stock_price

Latest price and currency for one ticker or company name. Resolves names such as LVMH to MC.PA. Returns an MCP error with suggestions when the symbol is unknown or the price is missing/zero. Not counted in the Score VI quota.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker or company name (e.g. AAPL, LVMH, MC.PA)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does meaningful work: it discloses ticker resolution (LVMH to MC.PA-adjacent mapping) and the error contract, including that unknown symbols return an MCP error carrying suggestions and that missing or zero prices are treated as errors. It adds no data for static metadata, but it does not mention latency, freshness, or market delay, which would eliminate all remaining doubt about a quote tool.

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?

Short and front-loaded: purpose first, then symbol resolution, then error behavior. The final note about Score VI quota is an operational aside rather than behavioral guidance, but it is one short clause and does not obscure the core.

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?

For a one-parameter read tool with no annotations and no output schema, the description covers what comes back (price and currency) and the failure modes (unknown symbol, missing/zero price). Only the response shape and quote freshness are left unstated, which are minor for this complexity.

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?

There is a single parameter at 100% schema coverage, and the schema already documents that a company name is accepted alongside a ticker, with examples. The description's note that names are resolved to symbols adds only marginal meaning beyond that, so the baseline is 3.

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: 'latest price and currency for one ticker or company name.' The word 'latest' implicitly distinguishes it from get_price_history, but no sibling is named explicitly, so the differentiation is inferred rather than stated.

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?

Usage is only implied by the phrase 'latest price' — an agent can guess this is the current-quote tool rather than a historical one, but there is no explicit when-to-use, when-not-to-use, or named alternative such as get_price_history.

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