Skip to main content
Glama

Change an order request

update_order_request
DestructiveIdempotent

Set an order request's status (new, confirmed, completed or cancelled) and/or its internal note, which only the team sees. The visitor is not told. Needs the Standard plan or higher.

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": {
      "request_number": "<request_number>"
    },
    "name": "update_order_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoThe new status.
internal_noteNoThe new internal note. It replaces the old one; an empty text removes it.
request_numberYesThe number, for example ORD-37779.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (which already flag destructiveHint=true and idempotentHint=true), the description discloses two behaviors the schema cannot: the note is internal-only ('only the team sees') and 'The visitor is not told', which is exactly what an agent needs before making a customer-affecting change. It does not warn about the consequences of overwriting a status or the irreversibility of a cancelled state, which the destructive annotation hints at but does not explain.

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 sentences with no filler: what is set, who can see it, and the plan requirement. The enum values repeated in prose are redundant with the schema and could be dropped without losing meaning.

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 three-parameter mutation with no output schema, the description covers the essential unknowns: scope of the change, visibility of the note, visitor notification behavior, and plan gating. It is close to complete; only the handling of an invalid status transition or missing request number is left unstated.

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 the schema already documents each parameter including the note-replacement and empty-string-removal semantics. The description mainly restates the status enum values, adding little parameter meaning beyond the visibility note for internal_note.

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 and resource ('Set an order request's status ... and/or its internal note') and enumerates the allowed status values, so an agent knows exactly what the tool changes. It is clearly a mutation of a single order request, distinguishable from the read-only get_order_request and list_order_requests siblings by implication rather than by name.

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: use it to move an order request between new/confirmed/completed/cancelled or to rewrite the internal note, and the description adds a real prerequisite ('Needs the Standard plan or higher'). It stops short of stating when not to use it (e.g. when only the visitor-facing message should change, or for bulk updates).

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