Skip to main content
Glama
mcp-gatehouse

mcp-gatehouse

list_orders

Read-only

List the orders on your desk with ID, customer, status, total, and notes; use this read-only view to find the order ID needed for lookup, notes, or cancellation.

Instructions

List the orders on the desk that are yours: id, customer, status, total and notes. Read-only. Start here to find the order ID that lookup_order, add_note and cancel_order need.

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": "list_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.6.1
    • addedOutput schema / $defs
      Added value: +{
      +  "Order": {
      +    "description": "One order on the desk.",
      +    "properties": {
      +      "customer": {
      +        "title": "Customer",
      +        "type": "string"
      +      },
      +      "id": {
      +        "title": "Id",
      +        "type": "string"
      +      },
      +      "notes": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "title": "Notes",
      +        "type": "array"
      +      },
      +      "owner": {
      +        "title": "Owner",
      +        "type": "string"
      +      },
      +      "status": {
      +        "title": "Status",
      +        "type": "string"
      +      },
      +      "total": {
      +        "title": "Total",
      +        "type": "number"
      +      },
      +      "version": {
      +        "default": 1,
      +        "title": "Version",
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "customer",
      +      "owner",
      +      "status",
      +      "total"
      +    ],
      +    "title": "Order",
      +    "type": "object"
      +  }
      +}
    • addedOutput schema / properties / result / items
      Added value: +{
      +  "$ref": "#/$defs/Order"
      +}
    • changedOutput schema / properties / result / type
      Previous value: -"string"New value: +"array"
  2. Addedv0.3.0

TDQS

A4.7/5.0
Behavior4/5

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

The read-only nature is already declared by readOnlyHint=true/destructiveHint=false, so restating "Read-only" adds no new information. What the description does contribute beyond annotations is the scoping rule (only your orders, only on this desk) and a preview of the fields returned, which helps the agent interpret results even though an output schema exists.

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?

Two short sentences, zero filler, with the purpose and scope front-loaded and the routing advice second. Every clause carries information an agent needs.

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

Completeness5/5

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

For a no-argument, read-only list tool with annotations and an output schema already in place, the description covers purpose, scope, and next-step routing. Nothing required to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so per the baseline there is nothing for the description to disambiguate. It correctly stays silent on arguments instead of inventing filtering options the schema does not support.

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?

States a specific verb and resource ("List the orders") plus a clear scope qualifier: orders on the desk that are yours. It also enumerates the returned fields and names the sibling tools that consume its output, so an agent can distinguish it from lookup_order/cancel_order/add_note without opening a schema.

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

Usage Guidelines5/5

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

Explicitly tells the agent to start here and explains why: to obtain the order ID that lookup_order, add_note and cancel_order require. That is a concrete when-to-use rule tied to named alternatives rather than an inferred one.

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

Deploy Server

Other Tools