Skip to main content
Glama

My calibration certificates

certificates_list
Read-onlyIdempotent

Your own Barmaan calibration certificates with live expiry state (valid, expiringSoon within 60 days, expired, revoked), newest or soonest-to-expire first. Filter by state (all, active, valid, expiringSoon, expired, revoked), q (serial, certificate code, equipment or manufacturer) or serial. Also returns counts. Demonstration samples are never listed. Page with page/limit.

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

Input Schema

NameRequiredDescriptionDefault
qNoSerial, certificate code, equipment or manufacturer.
pageNo
sortNo
limitNo
stateNoall
serialNoExact serial number (spaces/dashes/case ignored).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive/closed-world profile, and the description adds real behavior beyond them: the 60-day definition of 'expiringSoon', the default ordering ('newest or soonest-to-expire first'), the fact that counts are returned, and the exclusion of demo samples.

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?

Four tight sentences, front-loaded with what the tool returns and how results are ordered, followed by filter and paging notes. No filler and no repetition of the title.

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 6-parameter list tool with no output schema, the description covers ordering default, pagination, state semantics, and that counts are included. The remaining holes are the unexplained 'sort' parameter and the overlapping 'active'/'valid' states, which an agent would need to guess at.

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 only 33%, so the description carries weight: it explains q, serial matching, state values, and page/limit. But it never explains the 'sort' enum (expiryAsc/expiryDesc/issueDesc) and leaves the distinction between 'active' and 'valid' — both listed as states — ambiguous, which is the most consequential gap for a filtering tool.

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 pair ('your own Barmaan calibration certificates') with an explicit scope limiter ('your own', demo samples excluded), and the live expiry-state vocabulary immediately separates it from inventory tools like equipment_list or documents_list.

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 clear context for when this is the right call — personal certificates with expiry state, filterable by state/q/serial — and rules out demonstration samples. It does not name an alternative tool for other certificate scopes, so it stops short of explicit when-not guidance.

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