Skip to main content
Glama
Sign In

I Am Wallet

by io.github.ZKStamp
OverviewDiscussionsAdmin

deal_offer

DEALS (seller, step 1): offer a deal to another agent: a price per step, a number of steps (1 to 10) and what you deliver. Deals use small steps, no escrow: the buyer pays one step, you deliver it with a fingerprint, the buyer checks, and so on. Returns {ok, deal_id, txid, total_btcz, next}. The offer expires after about 24 hours. Shielded on the blockchain. Costs a 1 BTCZ service fee (the operator's coffee, paid to Z-TEXT LLC: probably the cheapest private coffee in the galaxy) plus a 0.0001 BTCZ network fee. 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": {
      "to": "<to>",
      "price": "<price>",
      "steps": "<steps>",
      "description": "<description>"
    },
    "name": "deal_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesBuyer's shielded address (zs)
priceYesPrice per step in BTCZ (max 500)
stepsYesNumber of steps, 1 to 10
descriptionYesWhat you deliver, short

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 so: it discloses the ~24h expiry, shielded-on-chain privacy, a 1 BTCZ service fee plus 0.0001 BTCZ network fee, the required 'Authorization: Bearer <key>' header, and the exact return shape {ok, deal_id, txid, total_btcz, next}.

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 and the operational facts (fees, auth, expiry) are all packed into one dense block. The parenthetical coffee joke is expendable, but it costs little and the rest 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?

For a 4-param mutation tool with no output schema and no annotations, the description supplies the payment model, cost, auth requirement, expiry, and return fields — everything an agent needs to invoke it correctly.

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 the baseline is 3. The description restates the semantics (price is per step, steps 1-10, description is what you deliver) but adds no format or validation detail beyond what the schema already documents.

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 ('offer a deal to another agent') plus the three defining inputs, and labels itself as the seller-side step 1, which cleanly separates it from 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 Guidelines4/5

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

The 'seller, step 1' framing plus the sketch of the no-escrow pay-deliver-check loop gives clear context for when to call this versus the later deal_* tools. It stops short of explicitly naming the siblings or stating exclusions, so it falls just below a 5.

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