Skip to main content
Glama

Get your service submitted to the agent venues we can reach, and to each new one as we add it (paid, x402)

placement_order

PAID: list your service on agent venues: we submit it to each venue we have a submitter for (17 of 33 today) and prove each entry landed, weekly for 90 days. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply. Price: $0.2500 USDC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "placement_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe order id, as returned when it was paid for.
urlNoThe absolute http(s) URL of YOUR service -- the one a venue should list. It must be publicly reachable: a loopback or private address is one no venue can verify.
dryRunNoOptional. true: a dry run -- nothing is sent or changed, and the 200 answer (served:true, dryRun:true) says what this call would do with the rest of your body, or which fields are missing. A dry run is a paid call at this price. false or absent: the call runs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / dryRun
      Added value: +{
      +  "description": "Optional. true: a dry run -- nothing is sent or changed, and the 200 answer (served:true, dryRun:true) says what this call would do with the rest of your body, or which fields are missing. A dry run is a paid call at this price. false or absent: the call runs.",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations only mark this as non-read-only and non-destructive, and the description goes well beyond them: it discloses the paid price, accepted chains and assets, the multi-venue submission and verification behaviour, the 90-day weekly cadence, and the no-individual-reply feedback policy. One tension: openWorldHint=false reads as 'no external world interaction' while the description says entries are pushed to 17 third-party venues — an agent may misjudge the blast radius.

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?

Front-loaded with 'PAID:' and the core promise, then payment, then feedback, then price — a sensible ordering with no filler. It is dense to the point of being crammed into one paragraph, but every clause carries information.

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 tool with full schema coverage and no output schema, the description covers cost, payment path, duration, coverage ratio and the dry-run semantics. The remaining gap is the order-id lifecycle — how an 'id' is obtained and reused for follow-up calls is not described.

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 100%, so baseline 3 applies. The description adds the payment mechanism that lives outside the declared schema (additionalProperties is false, yet _meta['x402/payment'] is required), but never explains the 'id' parameter's role or when it is needed versus a first-time 'url' submission.

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?

Specific verb and resource: 'list your service on agent venues', with concrete scope (17 of 33 venues, weekly for 90 days, proof of each entry). An agent knows exactly what this does. It stops short of naming the boundary against a plausible sibling such as listing_promote, so it is clear but not sibling-differentiated.

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

Usage Guidelines4/5

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

The invocation flow is spelled out: an unpaid call returns the price, then pay with x402 in _meta['x402/payment'] and call again, with a free feedback channel specified. What is missing is when to prefer this over adjacent listing/promotion siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources