Skip to main content
Glama

Trading Zones 4H Market Decisions

Get verifiable selector evidence

get_performance_evidence
Read-only

Fetch this free evidence before purchase. Returns the continuously updated TZ SELECT aggregate and a link to an independently countable rolling window of up to 100 latest settled choices. The rate does not describe every non-selected market package or guarantee future results.

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_performance_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safe-read profile (readOnlyHint, openWorldHint), and the description adds real value beyond them: the data is free, continuously updated, covers a bounded rolling window of 100 settled choices, and explicitly does not generalize to unselected packages or imply future results. It does not cover latency, authentication, or how the returned link should be consumed.

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?

Three sentences, front-loaded with the action and the timing constraint ('before purchase'), followed by contents and then the statistical caveat. Each sentence carries distinct information, though the marketing cadence ('free evidence') and jargon ('TZ SELECT aggregate') cost some precision.

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 parameters and no output schema, the description carries the full burden of describing return values, and it does: an aggregate rate plus a link to an independently countable rolling window. The caveat about non-selected packages and future results is exactly the kind of scope limit an agent needs, though what the 'aggregate' actually measures is left undefined.

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?

The tool takes zero parameters and the schema has 100% coverage, so there is no parameter semantics to explain. Baseline for a zero-argument tool is 4, and nothing in the description is needed to clarify inputs.

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 verb 'Fetch' and the resource 'evidence' are combined with a clearly named payload: the 'TZ SELECT aggregate' plus a link to a rolling window of up to 100 settled choices. The token-specific mention of TZ SELECT implicitly separates it from the BTC/ETH/XRP/ONDO setup siblings, though no sibling is named 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?

'Fetch this free evidence before purchase' gives an implied usage context that ties into the prepare_*_purchase siblings, but it never names prepare_tz_select_4h_purchase as the follow-on nor states any when-not-to-use condition. The agent can infer the workflow but must guess at the connection.

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