Skip to main content
Glama

Elliott Wave Atlas

Elliott Wave count for one market

get_market
Read-onlyIdempotent

The latest called Elliott Wave count for one market, made at its last completed close: the wave in progress, the price that invalidates the count, and for each timeframe (monthly, weekly, daily, hourly, 15-minute) the wave in progress, its target zone and its invalidation price. Returns Markdown, plus the same data as structuredContent (called_count, invalid_if, levels[]). Use list_markets or search_markets first if unsure which symbols are covered.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesThe market's symbol or name, case-insensitive. Examples: SPX, NVDA, BTC-USD (or bitcoin), GOLD (or gold), EURUSD, NIFTY. A leading $ is ignored. The closest match is used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / symbol / description
      Previous value: -"Symbol or name, e.g. BTC-USD, bitcoin, SPX, NVDA, gold, EURUSD"New value: +"The market's symbol or name, case-insensitive. Examples: SPX, NVDA, BTC-USD (or bitcoin), GOLD (or gold), EURUSD, NIFTY. A leading $ is ignored. The closest match is used."
    • addedInput schema / properties / symbol / maxLength
      Added value: +40
    • addedInput schema / properties / symbol / minLength
      Added value: +1
  2. First observed

TDQS

A4.2/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 settled. The description adds genuinely new behavioral context: the data is a snapshot 'made at its last completed close' and the response carries both Markdown and structuredContent (called_count, invalid_if, levels[]). Remaining gaps like behavior on unresolvable symbols are only partially covered by the schema's 'closest match is used' note.

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?

Purpose is front-loaded in the first clause, and the enumerated return fields earn their space because no output schema exists. Minor redundancy: 'the wave in progress' is stated twice (market-level and per-timeframe), which lengthens an already dense sentence.

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?

For a one-parameter read tool with no output schema, the description covers what it returns, in what format, at what point in time, and how to resolve a bad symbol. Nothing an agent needs to call it correctly is missing.

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?

With a single parameter at 100% schema coverage, the schema already documents case-insensitivity, the leading-$ rule, examples, and closest-match fallback. The description adds only the pointer that coverage can be checked via list_markets/search_markets, so 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?

The description names a specific verb and resource — 'the latest called Elliott Wave count for one market' — and enumerates exactly what is returned (wave in progress, invalidation price, per-timeframe target zones). It is clearly distinct from the sibling list/search tools, which only resolve symbols.

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?

It explicitly routes the agent to alternatives: 'Use list_markets or search_markets first if unsure which symbols are covered.' That is a concrete condition selecting a sibling. It does not state any when-not-to-use case, but for a read-only lookup tool the main ambiguity (bad symbol) is covered.

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