Skip to main content
Glama

My equipment

equipment_list
Read-onlyIdempotent

Your own instruments and equipment registered with Barmaan: name, make/model, serial, calibration due date and state (ok, due_soon within 60 days, overdue, unknown, not_applicable), service contract, and number of linked calibration certificates. Filter by q (name, serial, tag, model), category, due state, contract type, within_days (due in the next N days) or include_archived. Also returns a summary of counts. Page with next_cursor. Empty list = nothing registered yet.

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

Input Schema

NameRequiredDescriptionDefault
qNoName, serial, tag, model or manufacturer.
dueNoCalibration state filter.
sortNo
limitNo
cursorNoValue of next_cursor from the previous page.
categoryNo
contractNo
within_daysNoOnly equipment whose calibration is due in the next N days.
include_archivedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: that a summary of counts is returned, that paging uses next_cursor, that due_soon means within 60 days, and that an empty list means nothing is registered — details no annotation or schema conveys.

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 what the tool returns, followed by filter options and then paging/empty-result notes — a logical order with no filler. Every clause carries information an agent would otherwise have to guess.

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 9-parameter list tool with no output schema, the description covers the return payload, the summary counts, pagination, and empty-state meaning, which is most of what an agent needs. The remaining gap is sort and limit behavior (default page size of 10, cap of 25) that is only discoverable in the schema.

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?

With only 44% schema description coverage across 9 params, the description does real work: it explains the q fields, category, due state, contract type, within_days, include_archived, and that cursor comes from next_cursor. It omits sort and limit semantics, which remain undocumented in both places.

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 names the resource precisely ('Your own instruments and equipment registered with Barmaan') and enumerates the returned fields (name, make/model, serial, calibration due date, state, service contract, linked certificate count), so the agent knows exactly what a call yields. It does not explicitly distinguish itself from equipment_get or equipment_history, leaving that differentiation to name inference.

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?

Scope is implied by 'your own ... registered with Barmaan', and the filter list plus 'Empty list = nothing registered yet' gives practical context for interpreting results. However, there is no statement of when to prefer this over equipment_get (single record) or equipment_history, and no exclusions or prerequisites are given.

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