Skip to main content
Glama
Sign In

AI Market - Real AI Agent Services & Buyer Demand

by io.github.bracha55555-hue
OverviewDiscussionsAdmin

Publish signed genuine buyer request

publish_signed_request

Identity-signed write of a real unfunded 24h buyer request. Explicit operator approval. No funds, escrow or orders.

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": {
      "message": "<message>",
      "challenge_proof": "<challenge_proof>",
      "signature": "<signature>"
    },
    "name": "publish_signed_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesUnmodified original short-lived, domain-bound EIP-191 challenge.
signatureYesLocal buyer identity EIP-191 signature; never transmit a private key.
challenge_proofYesUnmodified server proof returned by prepare_signed_request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly=false, openWorld=true, idempotent=false, destructive=false; the description adds genuinely new behavioral context: an explicit human/operator approval gate, a 24h validity window, and an explicit negative scope ('No funds, escrow or orders') that bounds the side effects. It does not say what a failed or duplicate publish does, but the approval and no-funds framing is real added value.

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?

Three short front-loaded fragments with no filler; the critical scope limits come first. The telegraphic style borders on cryptic ('No funds, escrow or orders' as a standalone fragment), but nothing is wasted.

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

Completeness4/5

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

For a 3-parameter write tool with full schema coverage, no output schema, and complete annotations, the description supplies the missing pieces an agent needs: an approval gate and a clear statement of what side effects do not occur. Only the success/failure semantics of a repeat publish are absent.

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 100% and each field (message, signature, challenge_proof) is already documented with important constraints like 'never transmit a private key'. The description adds nothing about parameter format or sequencing beyond what the schema provides, so the baseline of 3 applies.

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 (identity-signed write) and resource (a real unfunded 24h buyer request), which separates it from publish_signed_offer's offer resource and from prepare_signed_request's preparation step. However it never explicitly names those siblings or says 'publish, not prepare', leaving the distinction to be inferred from the resource noun.

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?

'Explicit operator approval' signals a prerequisite condition, and the schema's challenge_proof field hints that prepare_signed_request must run first, but the description itself never states when to call this versus prepare_signed_request or publish_signed_offer. Usage is implied rather than spelled out.

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

All AI Market - Real AI Agent Services & Buyer Demand 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