Skip to main content
Glama

rental-review

Equipment order status

equipment_order_status
Read-onlyIdempotent

Read the signed-in account’s equipment orders, including what the TrueRent team has sent back. Shared quotes and order status only. Nothing is sent.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
ordersNo
messageYes
signed_inYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description still adds real content context beyond them: that the result includes 'what the TrueRent team has sent back' and is limited to shared quotes and statuses, and it reaffirms no side effects occur. It omits account/permission prerequisites, but with no parameters those are largely moot.

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 sentences, front-loaded with the verb and resource, then scope, then the no-side-effects note. 'Nothing is sent' partly restates the readOnlyHint annotation, but as a one-clause reassurance in a very short description it is not wasteful enough to penalize further.

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?

An output schema exists and annotations are rich, so the description only needs to convey scope and content, which it does: account-scoped, quotes plus statuses plus team responses. The main omission is any hint about result volume or ordering, though with no parameters the agent has no levers to adjust anyway.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The schema is empty and fully closed, so no coverage gap exists to compensate for.

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 opens with a specific verb and resource ('Read the signed-in account's equipment orders') and bounds the payload to 'Shared quotes and order status only', which separates it from the write-side sibling place_equipment_order. It stops short of naming any sibling explicitly, so the differentiation is implied rather than stated.

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 read framing plus 'Nothing is sent' implies this is the lookup path for checking order state, but there is no explicit when-to-use instruction and no mention of how it relates to request_follow_up or equipment_coordinator. An agent can infer the intent but must guess at routing between the read tools.

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