Skip to main content
Glama

Find supported markets

search_markets
Read-onlyIdempotent

Search the markets Premiss covers by name, ticker or alias (bitcoin, BTCUSDT, SPY, gold, oil): crypto, indices, commodities and US stocks. Returns registry ids with their class, tier (full, or history only with daily paper bots) and bar sizes. A miss returns the closest markets. Does not return prices or bars.

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": "search_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNo
limitNo
queryNo

Output Schema

NameRequiredDescriptionDefault
matchYes
marketsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changed
    • removedInput schema / properties / asset_class
      Removed value: -{
      -  "enum": [
      -    "crypto",
      -    "stock",
      -    "etf"
      -  ],
      -  "type": "string"
      -}
    • addedInput schema / properties / group
      Added value: +{
      +  "enum": [
      +    "crypto",
      +    "index",
      +    "commodity",
      +    "stock"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / maximum
      Previous value: -50New value: +60
    • removedOutput schema / properties / markets / items / properties / active
      Removed value: -{
      -  "type": "boolean"
      -}
    • addedOutput schema / properties / markets / items / properties / aliases
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / properties / markets / items / properties / assetClass
      Removed value: -{
      -  "enum": [
      -    "crypto",
      -    "stock",
      -    "etf"
      -  ],
      -  "type": "string"
      -}
    • addedOutput schema / properties / markets / items / properties / bar_sizes
      Added value: +{
      +  "items": {
      +    "enum": [
      +      "1m",
      +      "5m",
      +      "15m",
      +      "30m",
      +      "1h",
      +      "2h",
      +      "4h",
      +      "6h",
      +      "12h",
      +      "1d",
      +      "1w"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / properties / markets / items / properties / currency
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / markets / items / properties / exchange
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / markets / items / properties / group
      Added value: +{
      +  "enum": [
      +    "crypto",
      +    "index",
      +    "commodity",
      +    "stock"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / markets / items / properties / history_from
      Added value: +{
      +  "anyOf": [
      +    {
      +      "format": "date",
      +      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / markets / items / properties / hours
      Added value: +{
      +  "enum": [
      +    "24/7",
      +    "US market hours",
      +    "NYMEX trading days"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / markets / items / properties / kind
      Added value: +{
      +  "enum": [
      +    "crypto",
      +    "stock",
      +    "etf",
      +    "index",
      +    "commodity"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / markets / items / properties / paper_bar_sizes
      Added value: +{
      +  "items": {
      +    "enum": [
      +      "1m",
      +      "5m",
      +      "15m",
      +      "30m",
      +      "1h",
      +      "2h",
      +      "4h",
      +      "6h",
      +      "12h",
      +      "1d",
      +      "1w"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / markets / items / properties / status
      Added value: +{
      +  "enum": [
      +    "active",
      +    "live_only",
      +    "closing",
      +    "closed"
      +  ],
      +  "type": "string"
      +}
    • removedOutput schema / properties / markets / items / properties / symbol
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / markets / items / properties / tier
      Added value: +{
      +  "enum": [
      +    "full",
      +    "history_only"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / markets / items / required
      Previous value: -[
      -  "market",
      -  "symbol",
      -  "name",
      -  "assetClass",
      -  "exchange",
      -  "currency",
      -  "active"
      -]New value: +[
      +  "market",
      +  "name",
      +  "group",
      +  "kind",
      +  "tier",
      +  "aliases",
      +  "hours",
      +  "status",
      +  "history_from",
      +  "bar_sizes",
      +  "paper_bar_sizes"
      +]
    • addedOutput schema / properties / match
      Added value: +{
      +  "enum": [
      +    "exact",
      +    "closest",
      +    "all"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "markets"
      -]New value: +[
      +  "match",
      +  "markets"
      +]
  2. Changed1 schema field changed
    • removedInput schema / required
      Removed value: -[
      -  "query",
      -  "limit"
      -]
  3. 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 readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real domain context beyond that: results are registry ids with class, tier (full vs. history-only with daily paper bots) and bar sizes, and near-miss queries return closest markets instead of nothing. The only thing left implicit is whether results are ranked or paginated.

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?

Three sentences, each doing distinct work: what is searchable, what comes back, and what does not. The exclusion clause is placed last where it belongs, and the parenthetical examples are compact rather than padded. No sentence is redundant with the name or title.

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?

An output schema exists, so the description need not enumerate return fields, and it correctly restricts itself to explaining the non-obvious tier concept and the near-miss fallback. Annotations cover the safety profile. The main gap is that the group filter's role in narrowing results is never addressed, which matters for a search tool with a categorical filter.

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 0%, so the description must carry parameter meaning. It does explain the query parameter well (name, ticker, or alias, with four examples), but never mentions the group filter (crypto/index/commodity/stock) or the limit/pagination parameter, leaving two of three parameters documented only by their JSON types and bounds.

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?

States a specific verb and resource ("Search the markets Premiss covers") and enumerates both the lookup keys (name, ticker, alias) and the covered asset classes (crypto, indices, commodities, US stocks), so the agent knows exactly what universe is searchable. It also draws a return-value boundary ("Does not return prices or bars"), which implicitly separates it from lookup/reporting siblings, though it never names an alternative such as describe_market.

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?

Concrete query examples (bitcoin, BTCUSDT, SPY, gold, oil) convey intended use, and "A miss returns the closest markets" documents fallback behavior, which is genuinely useful when a search fails. However, there is no explicit when-to-use-vs-alternative statement, e.g. when to call this versus describe_market once an id is known, so the routing guidance is implied rather than stated.

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