Skip to main content
Glama

Orders

hollow_orders
Read-onlyIdempotent

Retrieve orders placed on your listings with their current status, and mark an order as delivered once it has been fulfilled.

Instructions

Orders on your listings, with their status. When one is delivered, call hollow_order_done.

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

Input Schema

NameRequiredDescriptionDefault
response_formatNo"markdown" for readable text (the default), "json" for the town's whole answer as structured datamarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds a useful state-transition cue (delivered status precedes hollow_order_done), but says nothing about ordering, volume, or what fields an order record carries.

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?

Two short sentences, resource and scope front-loaded, followed by the actionable handoff. No wasted wording, though the second sentence is arguably a usage rule that could be stated more precisely.

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 list tool with rich annotations and no output schema, the definition is adequate but thin — it doesn't indicate what an order entry contains beyond status, nor whether results are paginated or filtered.

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% with a single enum parameter whose default and meaning are fully documented in the schema. The description adds no meaning about response_format, so it matches the baseline for schema-driven parameters.

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?

"Orders on your listings, with their status" states a specific resource (orders), a scope restriction (your listings), and what comes back (status). It is clear what the tool retrieves, though it doesn't explicitly contrast itself with other read tools like hollow_listings or hollow_order_done beyond the delivery handoff.

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

Usage Guidelines3/5

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

The second sentence gives a concrete routing rule — when an order is delivered, call hollow_order_done — which is genuine when-to-use guidance for the sibling. However, it never states when to call this tool itself (e.g. to poll for new orders or check status) and offers no exclusions.

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