Skip to main content
Glama

Service history of one of my equipment items

equipment_history
Read-onlyIdempotent

Service history of one of your own equipment items, newest first (installation, calibration, inspection, maintenance, repair, part replaced, relocation, contract change). Filter by type or date range (from/to as YYYY-MM-DD). Page with next_cursor.

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": {
      "ref": "<ref>"
    },
    "name": "equipment_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoYYYY-MM-DD
refYesYour equipment reference (from equipment_list).
fromNoYYYY-MM-DD
typeNo
limitNo
cursorNoValue of next_cursor from the previous page.

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 readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description still contributes real behavior beyond them: result ordering (newest first), the taxonomy of event types returned, the filter dimensions, and cursor-based paging. It does not describe the record shape, which is the main remaining gap.

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?

Two dense sentences, front-loaded with what the tool returns, then ordering, then filtering and paging. The parenthetical event list is compact and earns its place by telling the agent what the type filter accepts.

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?

For a read-only, closed-world history query with annotations covering safety and no output schema, the description supplies ordering, filterable dimensions and pagination. It is nearly complete; only the returned record fields and paging termination (last page) are left unstated.

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 67% and the schema already documents ref (with format), from/to (YYYY-MM-DD), type enum, limit and cursor. The description mostly restates those formats rather than adding meaning; it does not clarify limit bounds or the difference between the request parameter `cursor` and the returned `next_cursor`. A baseline 3 is appropriate.

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 gives a specific verb+resource ("Service history of one of your own equipment items") and adds scope and ordering ("newest first"), which separates it from equipment_list (a catalog) and equipment_get (single-item detail). It stops short of naming a sibling explicitly, so it lands just under a 5.

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?

Usage is implied rather than stated: the agent learns it can filter by type or date range and page with a cursor, which tells it what the tool is for. There is no explicit guidance on when to prefer this over equipment_get, nor any precondition or exclusion (e.g. what to do when no history exists).

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