Skip to main content
Glama

Trading Zones 4H Market Decisions

Preview 4H products and check evidence for free

discover_4h_setups
Read-only

Free first step. Call with {} to find the BTC, ETH, XRP, ONDO or TZ SELECT 4H product, compare what is available and locate independently checkable performance evidence. No wallet is required. TZ SELECT selects at most one market per cycle. Use the free package when it satisfies the task; for a specific market, call prepare_4h_setup_purchase to check live availability and the exact payment budget for free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds genuinely non-structured facts: the call is free, no wallet or auth is required, and TZ SELECT covers at most one market per cycle. It stops short of describing the shape of the returned catalog, though 'compare what is available and locate independently checkable performance evidence' gives a rough sense.

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?

Front-loaded with 'Free first step' and the call signature, then the routing advice last. Slightly dense and mildly repetitive on the free/no-wallet point, but every sentence carries useful information.

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 zero-parameter, read-only discovery tool with no output schema, the description covers cost, auth requirements, the product set, cycle semantics for TZ SELECT, and the natural next tool. Only the returned content's format is left implicit, which is acceptable here.

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?

There are zero parameters, so the baseline is 4; the description usefully confirms the call takes an empty object ('Call with {}'), removing any doubt about whether arguments are expected.

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 uses concrete verbs (find, compare, locate) against a specific resource set (BTC, ETH, XRP, ONDO, TZ SELECT 4H products) and explicitly contrasts itself with prepare_4h_setup_purchase for single-market needs, so an agent can distinguish it from siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states both the positive case ('Free first step', 'Use the free package when it satisfies the task') and the alternative plus its trigger ('for a specific market, call prepare_4h_setup_purchase'), leaving nothing to inference about routing.

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