Skip to main content
Glama

get_elliott_waves

Read-only

Use when a technical trader needs wave counts, targets, and invalidation levels for major assets. Returns wave position, degree, target high/low, invalidation, and confidence for BTC, SPY, TLT, Gold. Example: wave label, target band, invalidation, and confidence score per asset. $0.50 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
assetNoAsset symbol or "all" (default all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, open-world, and non-destructive behavior. The description adds the important operational detail of $0.50 USDC per call and describes returned wave fields, though it omits freshness, latency, and data-source caveats.

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?

The definition is front-loaded with usage and outputs, then pricing. The example sentence largely repeats the return-field list, adding little beyond a per-asset illustration, so it is not maximally tight.

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?

With no output schema, the description carries the burden of explaining returns; it names the key output fields and covered assets. It still leaves open data recency, timeframe, and interpretation caveats for an open-world financial data tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the asset parameter is already documented. The description adds the supported asset universe (BTC, SPY, TLT, Gold), which helps an agent know valid symbol values beyond the generic schema wording.

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 analysis resource (Elliott wave counts) and lists the exact outputs and covered assets. It is clear enough to distinguish it from unrelated sibling tools, though it does not name an alternative for comparison.

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?

The opening 'Use when a technical trader needs...' gives a concrete usage scenario, and the asset list scopes coverage. It does not state exclusions or name an alternative for cases when this tool is not appropriate.

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