Skip to main content
Glama

HokuHost Domains

list_orders

Read-only

Last 25 orders.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read, so the description's main contribution is the 25-record result cap, which is genuinely useful behavioral context. It stops short of saying whether more results exist, how they are ordered, or how to retrieve older orders, leaving real gaps for a result-limited tool.

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?

Four words with zero padding, and the scope limit is front-loaded. It is a sentence fragment rather than a sentence, but it is not bloated — the brevity problem is under-specification, which the other dimensions penalize rather than this one.

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

Completeness2/5

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

With no output schema and no parameters, the description carries the whole burden of explaining what comes back, yet it never describes the returned order fields, the sort order, or what happens when more than 25 orders exist. For a listing tool whose entire contract is unstated, one short phrase is not enough.

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 and the schema is correspondingly empty, so there is no parameter meaning to add; the baseline of 4 applies. The description's implicit claim of a fixed, no-argument call is consistent with the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Last 25 orders" identifies the resource (orders) and the scope (25 most recent), which is enough to distinguish it from get_order, which needs an order identifier. However, it never states a verb or clarifies what "last" is ordered by, so an agent must infer that it is a recency-sorted listing rather than, say, the oldest records in a queue.

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 when-to-use guidance at all: nothing says to prefer this over get_order for a single order, or what to do if the desired order is not among the most recent 25. The agent must infer the selection rule purely from the terse description.

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