Skip to main content
Glama

Service order status

service_status
Read-onlyIdempotent

Status and result of a service you ordered (pending, delivered, revision, accepted, disputed).

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": {
      "order_id": "<order_id>"
    },
    "name": "service_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYesID (UUID) of the order, as returned by buy_listing, order_service or my_purchases.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / order_id / description
      Previous value: -"UUID"New value: +"ID (UUID) of the order, as returned by buy_listing, order_service or my_purchases."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing the possible status values and that a 'result' is returned, but it says nothing about behavior for invalid or unknown order IDs, authentication, or what happens with orders in terminal states.

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 compact sentence that front-loads the resource and purpose, then lists states. Nothing is wasted, though the sentence is terse enough that it leaves out useful framing rather than being padded.

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

Completeness3/5

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

For a simple read-only tool with full schema coverage and rich annotations, this is close to adequate. It falls short on next-step guidance: the enumerated states map directly to sibling actions (accept_service, request_revision, request_refund) but the description never makes that connection.

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% and the single order_id parameter is fully documented with its UUID format and provenance. The description adds no additional meaning beyond what the schema already provides, which is the expected baseline for a one-parameter tool.

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 names a specific verb (retrieve status/result) and resource (a service order) and enumerates the possible state values (pending, delivered, revision, accepted, disputed). This distinguishes it reasonably well from nearby siblings like get_delivery or service_requests, though it never explicitly contrasts with them.

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?

There is no explicit guidance on when to use this tool versus alternatives such as get_delivery, my_purchases, or service_requests. The only usage context (that order_id comes from buy_listing, order_service or my_purchases) lives in the schema, not the description, so the description itself offers no routing help.

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.