Skip to main content
Glama

FinanceQuery

Symbol Search

search
Read-onlyIdempotent

Search for stocks, ETFs, and companies by name or ticker symbol.

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>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoTarget language for translated text fields (BCP 47, e.g. "ja", "zh-Hant"); English or omitted = no translation
limitNoMaximum quotes per page; omitted = curated default (25)
queryYesSearch query string (company name or ticker symbol)
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

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?

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, so the safety profile is fully covered by structured data. The description adds nothing beyond that: no mention of pagination, result shape, cross-listing behavior, or that a symbol returned here feeds later calls. With annotations carrying the burden this is not a failure, but the text contributes no behavioral context.

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 zero wasted words. It is efficient but borders on terse for a five-parameter, paginated tool, so it stops short of a 5.

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?

Annotations and a fully documented schema cover the mechanics, and there is no output schema to explain. However, for a search entry point in a large catalog, the definition omits what to do with the results (e.g., pass a symbol to a details tool) and says nothing about pagination behavior despite cursor support.

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 coverage is 100%, so query, lang, limit, cursor, and fields are all documented in the schema itself. The description only restates that query accepts a company name or ticker, adding no syntax, matching behavior, or guidance on when to override fields/limit — baseline 3 is appropriate.

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?

Specific verb plus resource plus scope: searches stocks, ETFs, and companies by name or ticker symbol. An agent knows exactly what entity types come back, but the definition never contrasts itself with nearby tools like get_symbol_details or get_edgar_search, so differentiation is left to the agent.

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 'by name or ticker symbol' — the natural lookup-first step before a details call. There is no explicit when-to-use, when-not-to-use, or named alternative for retrieving full symbol details.

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.