Skip to main content
Glama

FinanceQuery

Ticker Lookup by Type

lookup
Read-onlyIdempotent

Discover tickers filtered by type (equity, ETF, mutual fund, index, future, currency, cryptocurrency).

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": {
      "query": "<query>",
      "query_type": "<query_type>"
    },
    "name": "lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoTarget language for translated text fields (BCP 47, e.g. "ja", "zh-Hant"); English or omitted = no translation
logoNoInclude logo URLs (requires an additional upstream API call); default: false
queryYesSearch query (company name or ticker symbol)
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set
query_typeYesFilter by type: equity|etf|mutualfund|index|future|currency|cryptocurrency (default: all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds no behavior beyond that — nothing about result caps, pagination, or the extra upstream cost implied by the schema's logo flag — and the parenthetical type list merely restates the query_type schema description.

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?

A single front-loaded sentence with the resource and filter stated first; nothing is wasted. Minor redundancy in enumerating the types that the schema already lists.

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 read-only search with full parameter coverage and annotations, the description is adequate but thin: it does not say what a result contains (ticker symbols only vs. names), whether results are capped, or how precise the query must be. Those omissions matter for an agent deciding whether one lookup suffices.

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 all five parameters (including lang, logo, fields, query, query_type) are already documented in the schema. The description adds no syntax or semantic detail beyond the type filter already spelled out in query_type, so the baseline of 3 applies.

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?

The description gives a specific verb ('Discover') and resource ('tickers') plus the filtering dimension ('by type'), which is more informative than the generic name 'lookup'. It is clear what the tool does, but it never positions itself relative to the many get_* siblings, so an agent must infer that this is the symbol-resolution entry point.

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: the wording suggests using this to find tickers by asset class, but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives. No note that this typically precedes calls like get_chart or get_financials, and no guidance on query phrasing.

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.