Skip to main content
Glama

Trading Zones 4H Market Decisions

Prepare an x402 setup purchase

prepare_4h_setup_purchase
Read-only

Use after choosing a market or TZ SELECT. Return the exact paid resource URL, $0.03 price ceiling, live readiness, free evidence link and wallet steps for one complete setup. The wallet-enabled agent signs and retries the returned HTTPS request; this preparation tool never moves funds.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesBTC, ETH, XRP or ONDO, or TZ-SELECT for the selector's current choice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is largely covered. The description still adds meaningful context the annotations do not: the $0.03 price ceiling, the no-funds-movement guarantee, and the sign-and-retry handoff to a wallet. It stops short of explaining what 'live readiness' means or what happens when a setup is not ready.

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?

Two sentences, front-loaded with the trigger condition and then the returned artifacts, with zero filler. Slightly dense phrasing ('live readiness, free evidence link and wallet steps for one complete setup') packs multiple concepts together but remains readable.

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 usefully enumerates what comes back (URL, price ceiling, readiness, evidence link, wallet steps) and states the next agent action. It leaves gaps around readiness semantics and failure modes, but for a one-parameter read-only preparation tool this is close to sufficient.

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 enum already documents BTC/ETH/XRP/ONDO plus TZ-SELECT's meaning, so the description adds nothing beyond the schema for the single parameter. Baseline 3 is appropriate when the schema carries the parameter documentation.

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 verb and resource with concrete outputs: exact paid resource URL, $0.03 price ceiling, readiness, evidence link, and wallet steps for one complete setup. It also clarifies the slightly misleading 'purchase' name by noting the tool never moves funds. It does not distinguish itself from the per-asset siblings (prepare_btc_4h_purchase, etc.), leaving the agent to infer that this one is the generic entry point via the symbol enum.

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?

'Use after choosing a market or TZ SELECT' gives a clear precondition, and the sentence about the wallet-enabled agent signing and retrying the returned request explains what happens next. There is no explicit when-not guidance or naming of an alternative (e.g., the per-asset tools), so the routing is implied rather than stated.

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