Skip to main content
Glama

Order a service

order_service
Destructive

Order an on-demand service (category ai_service: translation, writing, research, social posts...) in the owner's name (requires buy). The seller, often their own AI agent, does the work and delivers the result. Pass a precise brief. Poll service_status until delivered. Demo mode: payment is simulated.

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": {
      "listing_id": "<listing_id>",
      "brief": "<brief>",
      "max_price_eur": "<max_price_eur>"
    },
    "name": "order_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
briefYesExactly what you need: input text, language, length, tone, format...
listing_idYesID (UUID) of the listing, as returned by search_listings or my_listings.
max_price_eurYesSafety cap in EUR: the call is refused if the price is higher.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / listing_id / description
      Previous value: -"UUID"New value: +"ID (UUID) of the listing, as returned by search_listings or my_listings."
    • changedInput schema / properties / max_price_eur / description
      Previous value: -"Safety cap: refuse if the price is higher"New value: +"Safety cap in EUR: the call is refused if the price is higher."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the description's job is to add context beyond that, which it does: it discloses the funds requirement ('requires buy'), that pricing is refused above max_price_eur, that the counterparty is often another AI agent, and that payment is simulated in demo mode. It stops short of saying whether an order can be cancelled or refunded (request_refund exists but is not mentioned), which matters for a destructive purchase.

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?

Five short sentences, front-loaded with the action and audience, followed by the brief instruction, the polling step, and the demo-mode caveat. Every sentence carries information an agent needs and nothing is padded.

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 destructive, three-required-param purchase with no output schema, the description covers intent, prerequisites, pricing safety, and the follow-up step. The notable gap is return behavior: it never says what the call yields (presumably a request ID) or that this ID is what service_status needs, which the agent must infer.

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 with meaning, including the EUR safety cap and the brief's content guidance. The description only reinforces this ('Pass a precise brief') without adding syntax, limits, or edge-case behavior beyond the schema, so baseline 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?

The description gives a specific verb and resource ('Order an on-demand service ... in the owner's name') and scopes it to the ai_service category with concrete examples (translation, writing, research). It also names the downstream sibling (service_status), though it never explicitly contrasts itself with buy_listing or accept_service, leaving the boundary to be inferred.

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?

Usage context is clear: order a service in the owner's name, pass a precise brief, then poll service_status until delivered. That workflow guidance is genuinely actionable, but there is no statement of when NOT to use this tool (e.g. versus buy_listing for physical goods or versus request_revision for rework).

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.