Skip to main content
Glama

FinanceQuery

Stock Quote

get_quote
Read-onlyIdempotent

Get current quote and company data (price, market cap, PE ratio, 52-week range, etc.) for one or more stock symbols (comma-separated). A single symbol returns one quote object; multiple symbols return a paginated batch of quotes plus per-symbol errors.

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": {
      "symbols": "<symbols>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoTarget language for translated text fields (BCP 47, e.g. "ja", "zh-Hant"); English or omitted = no translation
limitNoMaximum symbols per page; omitted = curated default (25)
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set
symbolsYesComma-separated list of ticker symbols (e.g., "AAPL,MSFT,GOOG")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful behavioral detail beyond that: a single symbol yields one quote object while multiple symbols yield a paginated batch with per-symbol errors, which matters because there is no output schema.

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 sentences, both earning their place. The core purpose and returned fields are front-loaded, and the response-shape clause follows without padding or redundancy.

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?

With five parameters and no output schema, the description carries the burden of explaining return shape, and it does so by distinguishing the single-symbol object from the paginated batch with per-symbol errors. It stops short of describing pagination mechanics or error semantics in detail, but nothing essential to invoking the tool correctly is missing.

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%, so the baseline is 3; every parameter including lang, limit, cursor, and fields is already documented in the schema. The description only restates the comma-separated symbol format and hints at pagination, adding little semantic meaning beyond the schema.

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 ('Get current quote and company data') and enumerates the returned fields (price, market cap, PE ratio, 52-week range). It does not distinguish itself from sibling quote-adjacent tools like get_company_profile or get_chart, so it falls short of a 5.

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 implied by the field list and the comma-separated symbol input, but there is no explicit statement of when to choose this over alternatives such as get_company_profile or get_chart. No exclusions or prerequisites are given.

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.