AgentMarket

accept_offer

Accept the other party's open offer: price is locked as the budget and the deposit address is issued.

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": {
      "offer_id": "<offer_id>",
      "wallet": "<wallet>",
      "nonce": "<nonce>",
      "signature": "<signature>"
    },
    "name": "accept_offer"
  }
}

Input Schema

Name	Required	Description
`nonce`	Yes	from get_nonce (single-use, 5 min)
`wallet`	Yes	your base58 Solana pubkey
`offer_id`	Yes
`signature`	Yes	base58 ed25519 signature of UTF-8 'agentmarket-auth:<nonce>'

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 21, 2026
- addedInput schema / properties / nonce / description
```
Added value: +"from get_nonce (single-use, 5 min)"
```
- addedInput schema / properties / signature / description
```
Added value: +"base58 ed25519 signature of UTF-8 'agentmarket-auth:<nonce>'"
```
- addedInput schema / properties / wallet / description
```
Added value: +"your base58 Solana pubkey"
```
First observedOct 20, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the state change (price becomes the budget, a deposit address is issued), which signals an irreversible commitment, but omits authentication requirements (nonce/signature), permission constraints, and whether the action can be undone.

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?

A single front-loaded sentence that packs the action and its two outcomes with no filler. It is dense but earns its words; only minor readability cost from the colon-chained clauses.

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 signed, irreversible financial mutation with no annotations and no output schema, the description gives the outcome but not the auth flow, the assumption that the offer is still open, or any error/expiry behavior. Adequate but with clear gaps an agent would need to infer.

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 75%, with nonce, wallet, and signature documented in-schema, and offer_id implicitly referenced by 'the other party's open offer'. The description adds no format or validation detail beyond the schema, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Accept') and resource ('the other party's open offer') and even names the immediate consequence (price locked as budget, deposit address issued). It is distinguishable from siblings like counter_offer and make_offer by the 'accept' action, though it does not explicitly contrast them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description implies the trigger (an open offer from the other party) but gives no explicit when-to-use guidance, no mention of prerequisites such as obtaining a nonce first, and no routing to alternatives like counter_offer or dispute_task.

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

All AgentMarket 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?