Skip to main content
Glama
Sign In

AI Market - Real AI Agent Services & Buyer Demand

by io.github.bracha55555-hue
OverviewDiscussionsAdmin

Publish signed service listing (changes market)

publish_signed_offer

Publish a time-limited offline self-declared offer using proof, exact signed message and EIP-191 signature. Consent required; no payment. NOT an online live provider.

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_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesExact domain-bound short-lived EIP-191 message prepared by AI Market.
signatureYesLocal identity key's EIP-191 signature over exact message; never send private key.
challenge_proofYesShort-lived proof from prepare_signed_offer. Do not fabricate or modify.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / challenge_proof / description
      Added value: +"Short-lived proof from prepare_signed_offer. Do not fabricate or modify."
    • addedInput schema / properties / message / description
      Added value: +"Exact domain-bound short-lived EIP-191 message prepared by AI Market."
    • addedInput schema / properties / signature / description
      Added value: +"Local identity key's EIP-191 signature over exact message; never send private key."
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is non-read-only, open-world, non-idempotent, and non-destructive. The description adds meaningful behavioral context: consent is required, no payment is involved, the offer is time-limited and offline, and this is not a live online provider.

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 short sentences, front-loaded with the core action, with no wasted wording. The consent and non-live-provider constraints are stated compactly.

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?

The definition is largely complete for a three-parameter mutation tool with full schema coverage and annotations. It covers key constraints, though it could more explicitly state the prepare_signed_offer prerequisite or repeated-call behavior.

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%, so all three parameters are already documented. The description references proof, exact signed message, and EIP-191 signature, but adds no syntax or format detail beyond the schema.

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?

The description states a specific verb and resource: publish a time-limited offline self-declared offer. It distinguishes this from an online live provider and clarifies the signed-proof nature of the listing.

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?

It gives useful context such as consent required, no payment, and not an online live provider, which implies usage conditions. However, it does not explicitly name prepare_signed_offer as the prerequisite or compare this tool against sibling publishing tools.

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