Skip to main content
Glama

One of my calibration certificates

certificate_get
Read-onlyIdempotent

Details of one of your own certificates by its code: equipment, serial, dates, live state and days left, the recorded reading table, the public verification link, and earlier certificates for the same serial. Someone else's code returns not found. Values under as_recorded_on_certificate are exactly what was entered on the certificate; Barmaan makes no accreditation claim. The printable sheet is on the website (signed in): /portal/certificates//print.

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": {
      "code": "<code>"
    },
    "name": "certificate_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only, idempotent, non-destructive annotations, the description discloses access behavior (someone else's code returns not found), the data returned, the exactness caveat for as_recorded_on_certificate values, and a signed-in printable URL. This is unusually rich behavioral context for a read 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?

The description front-loads the core purpose and then packs useful return details, access behavior, and caveats without filler. Every sentence adds information an agent would need to select and interpret the tool correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only get-by-code tool with no output schema, the description explains the returned contents, access limitation, caveat about recorded values, and where the printable sheet lives. Nothing essential for correct invocation appears to be missing.

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 no schema description coverage, the description compensates by explaining that code identifies one of your own certificates and that using someone else's code yields not found. It does not add format examples beyond the schema pattern, but it gives meaningful ownership and lookup semantics.

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?

The description states a specific verb and resource: retrieving details of one of your own certificates by its code. It enumerates the returned information (equipment, serial, dates, live state, reading table, verification link, earlier certificates), making the scope far clearer than the title alone.

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?

It makes clear this is for one of your own certificates identified by code, and states that someone else's code returns not found. It does not explicitly name sibling tools such as certificates_list or verify_certificate as alternatives, so the routing guidance is strong but not fully explicit.

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