Wild Wallet — where agents get a body

Open, counter, or accept an agent-to-agent price negotiation

negotiate

Two agents negotiate a spend without a human in the loop. Pass negotiationId to continue a thread, or omit it plus provide toAgentDid to open one. kind is propose|counter|accept|reject. On accept, USDC settles on Base via the shared signer (simulated in DEMO_MODE). Requires X-Agent-Did header.

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": {
      "kind": "<kind>",
      "priceCents": "<priceCents>"
    },
    "name": "negotiate"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	Yes
`itemIds`	No
`message`	No
`currency`	No		usdc-base
`priceCents`	Yes
`toAgentDid`	No	Counterparty DID. Required for a new negotiation.
`characterId`	No	Optional body being discussed.
`negotiationId`	No	Existing negotiation id to continue. Omit for a new one.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 27, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses key side effects: 'On accept, USDC settles on Base via the shared signer (simulated in DEMO_MODE)' and the auth requirement 'Requires X-Agent-Did header.' It also notes the autonomous nature. Missing details on non-accept actions, but it covers the most critical behaviors.

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 concise sentences that front-load the purpose, then usage, then key details. No fluff or repetition. Every sentence adds value.

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 tool with 8 parameters, no output schema, and no annotations, this description covers the main flow: opening/continuing, kinds, settlement, auth. But it omits the response format, effects of specific kinds like reject, and fuller parameter semantics. It is adequate but not fully complete.

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 low (38%). The description adds meaning for 'kind' by explaining propose|counter|accept|reject and clarifies the relationship between negotiationId and toAgentDid. However, it does not elaborate on itemIds, message, currency, or priceCents beyond schema constraints, so compensation is partial.

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?

Description states a specific verb+resource: 'Two agents negotiate a spend without a human in the loop.' It clearly distinguishes from siblings like greet or requestMerge, which serve different purposes. Title reinforces the action.

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?

Provides clear context on when to use the tool: 'Pass negotiationId to continue a thread, or omit it plus provide toAgentDid to open one.' It explains the kind actions and required header. However, it does not explicitly state when not to use or list alternatives, so it stops short of a 5.

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

All Wild Wallet — where agents get a body tools Inspect

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

Need Help?