Compass by 402rates

Decode declared application and settlement metadata

decode_payment_attribution

Read-only

Free local decoding of an ERC-8021 schema-2 x402 builder-code suffix from supplied calldata. Separates application, facilitator, services and facilitator-reported metadata. No transaction lookup, receipt confirmation, identity verification or payment. Malformed and unsupported suffixes remain explicit.

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

Input Schema

Name	Required	Description	Default
`calldata`	No	Full caller-supplied transaction input as even-length 0x hex, at most 90,000 bytes. No URL, transaction hash, signature or receipt.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description adds meaningful behavioral context: decoding is free and local, no network lookup is performed, and malformed or unsupported suffixes are surfaced explicitly. It does not describe authentication or rate-limit behavior, but those are likely irrelevant for a local decoder.

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?

The description is compact and front-loaded: it names the decoding operation first, then explains what metadata is separated, what is excluded, and how malformed inputs behave. Every sentence adds useful information without repetition.

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?

For a one-parameter read-only decoder with full schema coverage and annotations covering safety, the description is nearly complete. It explains scope, exclusions, and malformed-input behavior, and it lists the metadata categories separated, though it does not describe the exact return shape in detail.

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 description coverage is 100%, and the single calldata parameter is fully documented in the schema with format and length constraints. The description only mentions 'supplied calldata' without adding syntax or format details beyond the schema, so the baseline score of 3 is appropriate.

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 verb and resource: decoding an ERC-8021 schema-2 x402 builder-code suffix from supplied calldata. It also scopes the tool by explicitly excluding transaction lookup, receipt confirmation, identity verification, and payment, which helps distinguish it from sibling payment-related tools.

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?

The description gives a clear usage context: use it on caller-supplied calldata when you need local decoding of builder-code metadata. It also provides useful exclusions by saying it does not perform transaction lookup, receipt confirmation, identity verification, or payment. It does not explicitly name an alternative sibling tool, so it falls short of the top score.

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

All Compass by 402rates 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?