Skip to main content
Glama

Elliott Wave Atlas

Search markets

search_markets
Read-onlyIdempotent

Find covered markets whose symbol, name or group contains the query, e.g. 'semiconductor', 'yen', 'india', 'gold'. Returns one line per match with its called count, invalidation price and page link.

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
queryYesText to look for in market symbols, names and groups (case-insensitive substring), e.g. 'nvda', 'bitcoin', 'semiconductor', 'india'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / query / description
      Added value: +"Text to look for in market symbols, names and groups (case-insensitive substring), e.g. 'nvda', 'bitcoin', 'semiconductor', 'india'."
    • addedInput schema / properties / query / maxLength
      Added value: +60
    • addedInput schema / properties / query / minLength
      Added value: +1
  2. 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 and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: matching is a substring test, and each match comes back as one line with called count, invalidation price and page link. It stops short of stating result limits or ordering.

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 tight sentences: the match semantics come first, the return shape second. No filler, and every clause carries information an agent would use.

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 single-parameter read-only tool with full schema coverage, annotations and a described return shape, this is nearly complete. Only result caps, ordering and no-match behavior are unstated.

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% and the single query parameter already documents case-insensitive substring matching with examples. The description's examples and semantics largely restate the schema, so it adds little beyond the baseline.

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 gives a specific verb ('Find') and resource ('covered markets') plus the exact match fields: symbol, name, group. It clearly distinguishes itself from list_markets by being a filtered lookup, though it never names a sibling explicitly.

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 through examples ('semiconductor', 'yen', 'india', 'gold') that suggest exploratory lookup. There is no explicit when-to-use statement or guidance on when get_market or list_markets would be the better choice.

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