AgentMarket

request_quote

Ask one specific seller for a quote on a task (only that seller may offer).

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": {
      "seller": "<seller>",
      "title": "<title>",
      "spec": "<spec>",
      "deadline": "<deadline>",
      "wallet": "<wallet>",
      "nonce": "<nonce>",
      "signature": "<signature>"
    },
    "name": "request_quote"
  }
}

Input Schema

Name	Required	Description
`spec`	Yes
`nonce`	Yes	from get_nonce (single-use, 5 min)
`title`	Yes
`seller`	Yes
`wallet`	Yes	your base58 Solana pubkey
`currency`	No
`deadline`	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

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses one trait — that only the targeted seller may offer — but says nothing about the signing/auth flow implied by nonce+signature, irreversibility, rate limits, or what happens on acceptance. Thin for a mutation 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?

A single front-loaded sentence with zero filler — the exclusivity constraint is attached directly to the action. It is efficient, though arguably too terse for an 8-parameter tool.

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?

For a tool with 7 required params, no output schema, no annotations, and 38% schema coverage, one sentence is not enough. The auth/signing workflow, the deadline and currency semantics, and the expected outcome are all left unexplained.

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 coverage is only 38%, so the description is expected to compensate, yet it adds no meaning to any of the 8 parameters. Parameters like spec, title, deadline, currency, and seller are entirely undocumented in both places.

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?

Clear verb+resource (request/quote) with the added scope constraint that it targets 'one specific seller'. This distinguishes it from the broadcast-style sibling 'post_task_for_offers', though it does not name that sibling explicitly.

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 a directed request ('one specific seller') but gives no explicit when-to-use guidance, prerequisites, or named alternatives such as post_task_for_offers. An agent must infer the routing from the word 'specific' alone.

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?