ExchangeRebel — pay-per-call APIs for AI agents (x402 on Solana)

dialect_precheck

FREE headline dialect pre-check (100/day per wallet; pass caller). Returns assessability only - whether the URL or artefact is in-policy; no fetch is performed, no artefact is analysed, no dialect finding is returned. The full signed report is the paid dialect_check call.

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": {
      "caller": "<caller>"
    },
    "name": "dialect_precheck"
  }
}

Input Schema

Name	Required	Description
`url`	No	Probe mode: the one endpoint URL whose live 402 challenge is fetched and graded. Never stored.
`mode`	No	The check mode: 'probe' (name one endpoint URL) or 'submitted' (submit one captured artefact set).
`caller`	Yes	Solana base58 wallet of the operator; keys the free allowance (100/day per wallet).
`artefact`	No	Submitted mode: one captured challenge/payload set (status?, body_obj?/body_raw?, header_obj?/payment_required_header?, payload_obj?, payload_headers?, response_headers?). Processed in memory only, never stored.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations, the description carries behavioral disclosure and does well on cost, rate limit, and output limits. However, 'no fetch is performed' conflicts with the schema stating probe mode fetches and grades a live 402 challenge, so the stated side-effect profile is not fully reliable.

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 front-loaded sentences communicate cost, return scope, limitations, and the paid alternative with no filler. The parenthetical efficiently packs the rate limit and required caller.

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

Completeness3/5

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

For a four-parameter tool with a nested artefact object and no output schema, the description gives the essential output scope and alternative. It still does not clarify the probe-vs-submitted behavior or exact response shape, and the no-fetch claim creates ambiguity about a core behavior.

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%, so parameter meanings are already documented in the input schema. The description reinforces that caller keys the free allowance and that the tool handles a URL or artefact, but adds no further syntax or mode details 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?

The description states a specific pre-check that returns only whether a URL or artefact is in-policy, and explicitly contrasts it with the paid dialect_check report. An agent can distinguish it from sibling dialect_check and dialect_criteria by scope and output.

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 names the free daily allowance, requires the caller wallet, and routes requests needing the full signed report to dialect_check. That gives an explicit use case, limitation, and alternative.

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

All ExchangeRebel — pay-per-call APIs for AI agents (x402 on Solana) tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?