Skip to main content
Glama

Search every market

search_markets
Read-only

Find any instrument OwlChart covers: crypto coins and perpetuals, stocks, ETFs, forex, indices, futures, commodities, bonds and economic series. Returns ids like crypto_perp:bybit:BTCUSDT or equity:NASDAQ:AAPL which the price history tool accepts.

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

Input Schema

NameRequiredDescriptionDefault
queryYesName, ticker, contract address or code, e.g. "bitcoin", "WLFI", "AAPL", "gold".

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 readOnlyHint=true and openWorldHint=true, so the safety and open-search profile is covered. The description adds useful context beyond that: the full breadth of asset classes searched and the exact shape of returned identifiers. It omits result-count limits, ranking/fuzzy-match behavior, and multi-match handling, which are the remaining behavioral unknowns for a search tool.

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, no filler, and the asset-class inventory is front-loaded before the return-format detail. Every clause carries information an agent needs: what can be found and what comes back.

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?

For a one-parameter search tool with full schema coverage and no output schema, the description correctly supplies the missing return-value contract (id examples) that the schema cannot. Slightly incomplete on result limits and behavior when multiple or zero instruments match, which matters for an open-world search.

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% on the single `query` parameter, and the schema already lists name, ticker, contract address and code with examples. The description adds only marginal meaning — that the query space spans perpetuals, indices, bonds and economic series — without new syntax or format rules. Baseline 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 states a specific verb (find/search) and a clearly bounded resource: all instruments OwlChart covers, enumerated across crypto, equities, ETFs, forex, indices, futures, commodities, bonds and economic series. It also pins down the output form (ids like crypto_perp:bybit:BTCUSDT) which makes the tool's role as a symbol-resolution step unambiguous. It does not differentiate itself against any named sibling such as arena_markets, 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 rather than stated: 'ids ... which the price history tool accepts' tells the agent this is the lookup step before requesting prices. There is no explicit when-not guidance, no mention of alternatives for market discovery, and no note on what to do when a query returns nothing or several matches. Adequate but inferential.

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.

Resources