Skip to main content
Glama
NullClear — Web3 Security & Tx Decoder

NullClear — Web3 Security & Tx Decoder

Official

nullclear_fetch_spot_price

Read-onlyIdempotent

Fetch verified cross-exchange spot prices for major crypto pairs, with positive-price invariant checks and signed attestation receipts to prevent hallucinated price data.

Instructions

Query cross-exchange spot prices (Coinbase + Binance) for major crypto pairs with deterministic positive-price invariant verification and signed attestation (10 free trials/day, then $0.01 USDC). Returns priceUsd, source, invariantCheck ('PASSED'), and execution receipt. Use this whenever a verified non-hallucinated crypto spot price feed is needed.

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": {
      "pair": "<pair>"
    },
    "name": "nullclear_fetch_spot_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairYesAsset ticker or pair such as 'ETH/USDC', 'BTC/USDC', 'SOL/USDC', or 'ETH-USD'ETH/USDC

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, but the description adds non-obvious behavior the agent cannot get elsewhere: dual-source aggregation, deterministic positive-price invariant check, signed attestation, a quota (10 free trials/day) and a cost ($0.01 USDC after). Pricing and rate-limit disclosure is exactly the kind of context annotations don't carry.

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 purpose and sources before the pricing and return details. Dense but no filler; the parenthetical pricing is somewhat crammed mid-sentence but every element earns its place.

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

Completeness5/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 compensates by naming the returned fields (priceUsd, source, invariantCheck, execution receipt). For a one-parameter read-only price tool, cost, sources, verification behavior, and return shape are all covered; nothing essential to correct invocation is missing.

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 single 'pair' parameter already has examples and a default, so the schema carries the semantics. The description adds only a soft constraint ('major crypto pairs'), which marginally narrows acceptable inputs but adds no format or normalization detail beyond the schema.

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?

States a specific verb and resource ('Query cross-exchange spot prices (Coinbase + Binance)') with explicit scope: major crypto pairs, invariant-verified, signed attestation. An agent immediately knows this is the verified price-oracle tool, distinct from escrow/contract/audit siblings.

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?

Gives a clear trigger: 'Use this whenever a verified non-hallucinated crypto spot price feed is needed,' which tells the agent the selection condition. It does not say when to avoid it or name an alternative, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.