Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-trading-signal

x402-trading-signal: On-chain signals. 🆓 5 free trial calls per signed wallet

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": "x402-trading-signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNo
tokenNo
addressNo
networkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / address / description
      Removed value: -"Address to process"
    • removedInput schema / properties / chain / description
      Removed value: -"Chain to process"
    • removedInput schema / properties / network / description
      Removed value: -"Network to process"
    • removedInput schema / properties / token / description
      Removed value: -"Token to process"
  2. First observed

TDQS

D1.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it barely does so. The single behavioral fact conveyed is "5 free trial calls per signed wallet," which hints that calls are metered, wallet-authenticated, and eventually paid, but says nothing about signal freshness, rate limits, latency, or whether the tool is read-only.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but brevity here reflects under-specification rather than efficiency. The only substantive sentence is an emoji-led pricing note, not the front-loaded purpose an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, zero-coverage, annotation-free tool with no output schema, this description is far too thin. It leaves unanswered what the tool returns, which inputs are required, and how to invoke it successfully.

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

Parameters1/5

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

All four parameters (chain, token, address, network) have 0% schema description coverage, and the description supplies no meaning for any of them. It does not clarify the relationship between chain and network, whether address is a wallet or contract, or which parameters are needed for a useful call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description offers only the noun phrase "On-chain signals" for the trading-signal tool, which essentially restates the name rather than specifying what a signal is, what chains/tokens are covered, or what form the output takes. It does not distinguish this tool from siblings such as x402-onchain, x402-poly-signals, or x402-token-signal.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no indication of which chains or tokens are supported. The only contextual claim, the free trial allotment, is pricing information rather than usage guidance.

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.