Skip to main content
Glama

Find stock tickers and company listings

search_stocks
Read-only

Resolve a company name, native ticker, ISIN or exchange-qualified symbol to Bullrun listings before calling exact-ticker research tools. Supports exchange/MIC, country, currency and instrument-type filters. Recognized exchange suffixes are checked against compatible stored venues; dots in native share-class tickers are preserved. Returns explicit ambiguous candidates and never picks a listing when alternatives remain. No enrichment or market-data refresh. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum output candidates. A backend scan is capped at 500 candidates per search.
queryYesCompany/name phrase, exact native ticker (AAPL, BMW, BRK.B), ISIN, EXCHANGE:TICKER, or exchange-suffixed symbol (BMW.DE, NESN.SW).
countryNoExact stored country name, e.g. Germany or Switzerland.
currencyNoListing quote currency, e.g. USD, CHF or GBX. GBX and GBP are different quote units.
exchangeNoStored exchange code or supported MIC, e.g. XETRA/XETR, NASDAQ/XNAS, SW/XSWX. A conflicting prefix is rejected.
quoteTypeNoDefault stocks, including unclassified equities. ETF/ALL allow other instrument lookup; this does not make stock-only research tools valid for funds.EQUITY
includeInactiveNoInclude inactive/retired listings. Returned lifecycle/successor fields must be checked.
includeSecondaryNoInclude alternative venue listings. ISIN/name matches across venues require an explicit listing choice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Company/name phrase, exact native ticker (AAPL, BMW, BRK.B), ISIN, EXCHANGE:TICKER, or Yahoo symbol (BMW.DE, NESN.SW)."New value: +"Company/name phrase, exact native ticker (AAPL, BMW, BRK.B), ISIN, EXCHANGE:TICKER, or exchange-suffixed symbol (BMW.DE, NESN.SW)."
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnlyHint and destructiveHint, yet the description adds genuinely non-obvious behavior: suffix checks against compatible stored venues, preservation of dots in share-class tickers, and the disambiguation contract ('never picks a listing when alternatives remain'). It does not describe result shape or how ambiguity is surfaced structurally, which keeps it below 5.

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?

Front-loaded with the core purpose and reasonably dense, with no filler sentences; the disambiguation and no-enrichment statements each carry weight. Four sentences plus a terse 'Read-only' tag is close to ideal, though the venue-suffix sentence is the densest and slightly opaque on first read.

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 no output schema, the description carries the return-value burden and does address it partially ('Returns explicit ambiguous candidates'), which is the key contract for a resolver. Given 8 parameters all schema-documented and read-only annotations present, this is nearly complete; only the concrete candidate fields returned are left implicit.

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 schema already documents every parameter including the GBX/GBP distinction and the exchange-prefix rejection rule. The description adds only a summary of allowed filter categories (exchange/MIC, country, currency, instrument-type), which the schema states more precisely. Baseline 3 applies.

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?

States a specific verb+resource ('Resolve a company name, native ticker, ISIN or exchange-qualified symbol to Bullrun listings') and positions it relative to siblings by saying it runs 'before calling exact-ticker research tools.' An agent can distinguish it from screen_stocks or search_etfs without opening schemas, since this is identifier resolution rather than criteria screening.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear when-to-use ('before calling exact-ticker research tools') and a when-not boundary ('No enrichment or market-data refresh'), which likely routes agents to the get_* research tools instead. It does not name a specific alternative tool by name, so it stops short of the explicit alternative-routing that would earn a 5.

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.