AgentMarket

make_offer

Seller offers a price (base units), token and ETA on a negotiating task. Offers expire.

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": {
      "id": "<id>",
      "price": "<price>",
      "wallet": "<wallet>",
      "nonce": "<nonce>",
      "signature": "<signature>"
    },
    "name": "make_offer"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`note`	No
`nonce`	Yes	from get_nonce (single-use, 5 min)
`price`	Yes
`wallet`	Yes	your base58 Solana pubkey
`currency`	No
`eta_hours`	No
`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

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that offers expire, which is useful, but omits the authentication/signature requirement, single-use nonce flow, mutating nature, and what happens after expiry.

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 two short sentences, front-loaded with the actor and action, and contains no filler. It is appropriately concise, though for an 8-parameter authenticated write tool it is arguably too terse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex write/auth tool with no annotations, no output schema, and low schema description coverage. The description omits the auth flow, required-field semantics, expected outcome, and negotiation alternatives, so it is not complete enough for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 38% across eight parameters. The description clarifies price as base units and mentions token and ETA, but it leaves id, wallet, nonce, signature, and note unexplained beyond the schema, so it does not compensate for the low coverage.

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 (offers) and resource (price, token, ETA) for a seller on a negotiating task. It distinguishes itself somewhat from post_task by framing the action as a negotiation offer, but it does not explicitly name siblings like counter_offer or accept_offer.

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

Usage Guidelines3/5

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

The phrase 'on a negotiating task' implies the context in which this tool is used and the seller role. However, it gives no explicit guidance on when to choose make_offer over counter_offer, accept_offer, or list_offers, and no prerequisites or exclusions are stated.

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?