Skip to main content
Glama

rental-review

Place an equipment order

place_equipment_order
Idempotent

Place an equipment order for a signed-in TrueRent account. Call only after the person confirms the equipment, the place, and the date. The TrueRent team is notified. No vendor is contacted from this step. TrueRent places the order after the customer clicks OK. Without a TrueRent account, tell them they need one. Do not send a follow-up in place of the order.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "confirmed": "<confirmed>",
      "equipment": "<equipment>"
    },
    "name": "place_equipment_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
job_zipNoJob ZIP, if there is no street.
projectNo
durationNo
quantityNoHow many. 1 to 999.
confirmedYesTrue only after the person confirms the order.
equipmentYesEquipment needed.
job_numberNo
delivery_dateNoYYYY-MM-DD.
idempotency_keyNoOptional stable key so a repeat does not create a second order.
delivery_locationNoWhere it goes.

Output Schema

NameRequiredDescriptionDefault
refNo
messageYes
receivedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, non-destructive, idempotent, closed-world write, so the safety profile is covered. The description still adds real process context: the TrueRent team is notified, no vendor is contacted at this step, and TrueRent places the order only after the customer clicks OK. It does not describe what happens on duplicate submissions, failures, or whether the order can be cancelled, which matters for a mutation tool.

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?

Front-loaded with the core action, then preconditions, then downstream behavior, then failure/edge guidance. Every sentence contributes a distinct constraint and none repeat the schema or annotations.

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, so return values need no explanation, and annotations cover the safety profile for this idempotent write. The description covers the confirmation gate, account prerequisite, and order-placement flow, leaving only edge cases like duplicate orders and error handling unaddressed.

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?

With 64% schema description coverage across 11 parameters, the schema carries most of the weight. The description does sharpen the meaning of the required 'confirmed' flag by tying it to confirmation of equipment, place, and date, but says nothing about quantity, delivery_date, delivery_location, or idempotency_key behavior that isn't already in the schema.

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 ('Place an equipment order') scoped to a signed-in TrueRent account. The sentence 'Do not send a follow-up in place of the order' implicitly separates it from request_follow_up, and 'No vendor is contacted from this step' separates it from a coordinator/status flow, so an agent can route correctly without opening a sibling schema.

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

Usage Guidelines4/5

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

Gives an explicit precondition ('Call only after the person confirms the equipment, the place, and the date') plus a blocking condition ('Without a TrueRent account, tell them they need one') and a negative instruction about substitutes. It stops short of naming sibling tools as alternatives, but the when-to-use and when-not signals are clear and actionable.

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