Skip to main content
Glama

Trading Zones 4H Market Decisions

Prepare TZ SELECT 4H x402 purchase

prepare_tz_select_4h_purchase
Read-only

Use when the user wants a current TZ SELECT 4H setup with entry, liquidity-zone SL/TP and nine indicators. Return the exact paid URL, free evidence link and wallet steps. No funds move until the wallet or user authorizes the x402 request.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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, and the description adds important safety context: 'No funds move until the wallet or user authorizes the x402 request.' That is consistent with a read-only preparation step and clarifies the authorization boundary. It does not cover rate limits or the full x402 flow, so it stops short of a 5.

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?

Three tight sentences: trigger, returned artifacts, and safety guarantee. It is front-loaded with the usage condition and every sentence contributes distinct 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?

With no output schema, the description helpfully lists what is returned: the exact paid URL, free evidence link, and wallet steps. For a zero-parameter preparation tool this is nearly complete, though it could say more about how it relates to get_tz_select_4h_setup or generic prepare_4h_setup_purchase.

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 has zero parameters, so there is nothing to misinterpret and the baseline is 4. The description does not need to compensate for missing parameter 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 says this prepares a purchase for a current TZ SELECT 4H setup and enumerates the deliverables: paid URL, free evidence link, and wallet steps. It is clearly specific to TZ SELECT 4H, so an agent can distinguish it from generic purchase tools, though it does not explicitly contrast with siblings like prepare_4h_setup_purchase or get_tz_select_4h_setup.

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?

It gives a clear trigger: 'Use when the user wants a current TZ SELECT 4H setup...'. It does not explicitly state when not to use it or name alternatives, but the context for selection is unambiguous.

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