Skip to main content
Glama

Little Works

materials_order_status

Materials PO lifecycle: pending → ordered → received. How buyer, ops, and manufacturer see the transaction.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden, and it discloses little: it does not say whether the call is read-only, what data comes back, or whether it reflects a single order or a collection. The lifecycle-state and multi-perspective framing is the only behavioral hint. For a tool with no annotations and no output schema, this leaves the agent guessing about the response shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short with no filler, which is good, but it is structured as two cryptic fragments rather than a front-loaded statement of what the tool does. The arrow notation and 'How buyer, ops, and manufacturer see the transaction' are evocative but not self-explanatory, so brevity costs clarity here.

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 annotations, the description is the only source of truth about results, yet it never explains the return format, whether status is returned per order, or how the three perspectives are surfaced. For a zero-parameter status tool the bar is low, but the agent still cannot form an expectation of the response.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. Schema coverage is reported at 100%, and there are no arguments whose meaning could be lost.

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?

The description names the resource (materials PO lifecycle) and enumerates the states (pending → ordered → received), which hints that this reports order status. But it never states a verb or what the tool actually returns, and the second fragment ('How buyer, ops, and manufacturer see the transaction') is more of a framing note than a purpose statement. An agent can guess this is a status-inspection tool but cannot confirm it from the text alone.

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 and no comparison to any sibling, even though nearby tools such as get_hold_status, list_materials, and draft_materials_order plausibly overlap. The agent is left to infer that this is the right call for checking PO state versus listing or drafting orders. No prerequisites or exclusions are stated.

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