Skip to main content
Glama
Sign In

I Am Wallet

by io.github.ZKStamp
OverviewDiscussionsAdmin

deal_check

DEALS (buyer): check a delivered step against the seller's signed fingerprint. Free (no transaction). For a result inside the message it checks automatically; for a link, compute the downloaded file's SHA-256 yourself and give it as 'fingerprint' (or its text as 'content'): the server never downloads the file. A NO MATCH blocks your next deal_pay until a check gives MATCH. Returns {ok, match, verdict, fingerprint_sha256, txid, seller_signer}. A match proves which result was delivered and when, not that the work is good. Needs the header 'Authorization: Bearer ' (your wallet key from create_wallet).

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": {
      "deal_id": "<deal_id>"
    },
    "name": "deal_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepNoStep to check (default: the latest delivered)
contentNoOptional: the text you received, to fingerprint
deal_idYesThe deal id
fingerprintNoOptional: SHA-256 of the file you downloaded

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does: it discloses that the call is free (no transaction), that the server never downloads the file, the exact return fields, the auth header requirement, and a crucial caveat that a match proves delivery provenance, not work quality.

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?

Front-loaded with purpose, then usage branching, then return shape and auth. Every sentence earns its place, though the dense run-on parentheticals ('(or its text as "content")', '(your wallet key from create_wallet)') slightly reduce scannability.

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?

There is no output schema, and the description compensates by enumerating the return keys and their meaning. Combined with the auth note and the blocking rule, an agent has everything needed to invoke it correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining when to supply 'fingerprint' (downloaded file) versus 'content' (message text) and clarifying that step defaults to the latest delivered.

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 ('check a delivered step against the seller's signed fingerprint') and scopes it as the buyer-side deal tool. It is clearly distinguishable from siblings like deal_pay, deal_deliver, and deal_status.

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?

Explicitly branches usage: in-message results are checked automatically, while link results require the caller to compute SHA-256 and pass 'fingerprint' or 'content'. It also states the blocking consequence ('A NO MATCH blocks your next deal_pay until a check gives MATCH'), which tells the agent when this call is mandatory.

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

All I Am Wallet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources