Skip to main content
Glama

Get one of my equipment items

equipment_get
Read-onlyIdempotent

Details of one of your own equipment items by ref: identity, serial, calibration state and due date, service contract, linked calibration certificates (open them on the website while signed in) and the latest service history. Someone else's ref returns not found. Free text is wrapped as data.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesYour equipment reference (from equipment_list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world, and non-destructive, so safety is covered. The description adds real value beyond them: the ownership scoping rule and its not-found outcome, the fact that certificate links are not openable in-tool, and that free text is wrapped as data (an injection-safety signal). It does not describe response shape, but no output schema exists and the field list substitutes reasonably.

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?

Two sentences, front-loaded with the operation and scope before the returned-content list. Dense but each clause carries information; the parenthetical about opening certificates on the website is slightly interruptive but earns its place as a behavioral caveat.

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?

With no output schema, the description compensates by enumerating the returned fields, and it explains the ownership constraint and the not-found outcome for an out-of-scope ref. An agent has enough to call it correctly; only the exact error/response structure is left unstated, which is minor for a single-ref read.

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 100% and the single ref parameter already carries its regex pattern and the 'from equipment_list' sourcing hint. The description only restates 'by ref' without adding format, casing, or example syntax, so it does not go meaningfully beyond the schema.

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 states a concrete operation on a concrete resource ('Details of one of your own equipment items by ref') and enumerates the content areas returned: identity, serial, calibration state/due date, service contract, linked certificates, and latest service history. The 'your own' scope separates it from a general item lookup, though it never explicitly names equipment_list or equipment_history as the sibling with which it could be confused.

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: fetch a single item by a known ref, with the schema noting refs come from equipment_list. It also gives one useful negative case ('Someone else's ref returns not found') and a practical note that certificates must be opened on the website while signed in. There is no explicit when-to-use-this-vs-equipment_history or equipment_list statement.

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