Skip to main content
Glama
Sign In

I Am Wallet

by io.github.ZKStamp
OverviewDiscussionsAdmin

deal_pay

DEALS (buyer): pay the NEXT step of a deal offered to you (find the deal_id in inbox or deal_status). Step 1 can be paid right away; each later step only after the previous one was delivered, and never right after a NO MATCH from deal_check (check again, or set force=true). Starter gift coins can pay up to 100 BTCZ of deals with other I Am Wallet wallets. Returns {ok, deal_id, step_paid, of_steps, paid_btcz, txid, next}. 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": {
      "deal_id": "<deal_id>"
    },
    "name": "deal_pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoPay even though your last check said NO MATCH (default false)
deal_idYesThe 8-character deal id from the offer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / force
      Added value: +{
+  "description": "Pay even though your last check said NO MATCH (default false)",
+  "type": "boolean"
+}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly: it discloses the 1 BTCZ service fee, 0.0001 BTCZ network fee, gift-coin limit, shielded transaction property, auth header requirement, and even the return object keys. These are exactly the behavioral details an agent needs before invoking a payment tool.

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?

The description is front-loaded with the core action, sequencing constraints, and deal_id source before costs and auth details. It is somewhat long and includes a coffee joke that does not strictly earn its place, but the length is mostly justified by the number of operational constraints being communicated.

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?

Given there are no annotations and no output schema, the description is complete enough for correct invocation: it covers prerequisites, sequencing, fees, auth, gift-coin limits, and expected return fields. No critical behavioral or contextual gap remains for this two-parameter payment tool.

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 useful meaning beyond the schema: it says the deal_id comes from inbox or deal_status, and it explains the force parameter in the context of a prior NO MATCH check. It does not add syntax details, but the additional sourcing and precondition context justify a 4.

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: paying the next step of a deal offered to the buyer. It distinguishes this from sibling tools by pointing to deal_check, deal_status, and inbox for context, so an agent can identify the operation without opening the schema.

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 gives explicit when-to-use rules: step 1 can be paid immediately, later steps only after prior delivery, and payment should not happen right after a NO MATCH from deal_check unless force=true. It also tells the agent where to find deal_id, leaving little ambiguity about invocation conditions.

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