Skip to main content
Glama

Listing Search

SearchListings
Read-only

Find exchange listings by company name or ticker (query), by ISIN (isin), or list every listing of one exchange or country, across the US and other exchanges. Each row gives the symbol other tools accept (a bare ticker for a US listing, MIC:TICKER such as XETR:SIE for another exchange), the company, country, trading currency, ISIN, security type and whether it is the company's main listing. An ISIN returns every listing of that security, each in its own currency; a US or Canadian ISIN also matches a US listing by its CUSIP. Use ListExchanges for the exchange and country codes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "SearchListings"
  }
}

Input Schema

NameRequiredDescriptionDefault
isinNoISIN to look up (e.g. IE00B5BMR087); not combined with query.
queryNoCompany name or ticker to search for (e.g. siemens, ASML, XETR:SIE).
marketNoCountry code whose listings to list (e.g. US, DE, PT); used on its own.
offsetNoRows to skip before returning results (default 0).
exchangeNoExchange code to keep or list (e.g. XETR, XAMS, XLIS); see ListExchanges.
maxResultsNoMaximum rows to return (default 20, max 500).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses important behavioral details: the output row fields, the symbol format returned for US versus non-US listings, and that an ISIN returns every listing in each currency, including CUSIP matching for US/Canadian ISINs. These are material behaviors an agent needs to interpret results correctly.

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?

The description is front-loaded with the tool's purpose, then layers in output format and matching behavior without filler. Every sentence contributes either selection guidance or result interpretation guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description appropriately explains the returned row fields and symbol formats. It also covers all search modes, including the ISIN multi-listing case, making the definition complete for a six-parameter read-only search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is already strong. The description adds useful meaning beyond the schema by explaining the symbol conventions and ISIN multi-listing behavior, though most individual parameter semantics are still carried by the schema.

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?

The description starts with a specific verb and resource: 'Find exchange listings.' It clearly distinguishes the three search modes (company/ticker query, ISIN, or exchange/country listing) and the geographic scope, so an agent can tell exactly what this tool does.

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?

The description explains how to use each main mode and points to ListExchanges for exchange and country codes. It does not explicitly state when not to use this tool versus other security-search siblings, but the usage context is clear enough for correct selection.

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.