Skip to main content
Glama

Elliott Wave Atlas

List covered markets

list_markets
Read-onlyIdempotent

Every covered market (about 100) with its latest called Elliott Wave count in one line, the date of the close it was made at, its invalidation price and a link to its page. Optionally limited to one group.

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

Input Schema

NameRequiredDescriptionDefault
groupNoOptional. Only markets in this group (case-insensitive, partial match). Groups: US indices, US stocks, Sector & country ETFs, Crypto, Commodities, World indices, Rates & FX, India, China & HK, Korea, Japan, Taiwan, Europe. Omit for every market.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / group / description
      Previous value: -"e.g. Crypto, US stocks, US indices, Commodities, Rates & FX, India"New value: +"Optional. Only markets in this group (case-insensitive, partial match). Groups: US indices, US stocks, Sector & country ETFs, Crypto, Commodities, World indices, Rates & FX, India, China & HK, Korea, Japan, Taiwan, Europe. Omit for every market."
    • addedInput schema / properties / group / maxLength
      Added value: +40
  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 read-only, idempotent, non-destructive, and closed-world behavior, so the description appropriately adds return-content context: roughly 100 markets, one line per market, latest count, close date, invalidation price, and link. It does not discuss pagination or output format beyond this, but little more is warranted for a fixed read listing.

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 a single efficient sentence that front-loads the full scope and then lists returned fields. Every clause earns its place by clarifying what the agent will get 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 simple read-only listing with one optional parameter and rich annotations, the description does enough: it explains the scope, approximate size, per-market return fields, and optional group restriction. Minor gaps like ordering or exact formatting are not critical for correct invocation.

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 schema already documents the group filter, accepted group names, case-insensitive partial matching, and omission behavior. The description adds only 'Optionally limited to one group,' which restates the schema rather than adding new syntax or semantics.

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 clearly states the resource and scope: every covered market (about 100) with its latest Elliott Wave count, close date, invalidation price, and page link. It distinguishes the bulk listing from single-market or search tools only implicitly by emphasizing 'every covered 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?

It implies usage by noting the optional group filter, but does not explicitly say when to use this instead of search_markets or get_market. The agent can infer it is for broad listing, yet no alternatives or exclusions are named.

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