Skip to main content
Glama

repairinfo: repairability of devices

Device details

get_device
Read-onlyIdempotent

All data for one device: score and what it is based on, repairability class and index, guaranteed software update years and the year updates last until at least, user-replaceable battery, battery life, charge cycles, spare-part years, energy class, EPREL registration number, official recalls or safety warnings (EU Safety Gate, RappelConso) if any, and the link to the device page.

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": {
      "id": "<id>"
    },
    "name": "get_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDevice id from search_devices or top_devices, e.g. smartphones/gigaset-gs6-pro

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond that by enumerating the returned payload, including that recalls can come from external registries (EU Safety Gate, RappelConso) and that a device-page link is included. It does not state what happens for an unknown or malformed id, which is the 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence that states the tool's scope before the field list, with no filler or marketing language. The long comma-separated field enumeration is dense but every item is informative rather than redundant.

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?

With no output schema, the description must convey what comes back, and it does so exhaustively for a single-record read tool. Combined with the annotations and the well-documented id parameter, an agent has everything needed to call and interpret it.

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?

There is a single parameter with 100% schema coverage and a concrete example format (smartphones/gigaset-gs6-pro), so the schema carries the burden fully. The description adds no syntax, format, or validation meaning beyond it, making baseline 3 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?

"All data for one device" names the resource and scope (retrieve-everything for a single device), and the field enumeration makes clear it is a detail endpoint rather than a list or barcode lookup. It never explicitly contrasts with search_devices or lookup_barcode, so sibling differentiation is only implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use or when-not-to-use guidance and names no alternative. The only workflow hint (that the id comes from search_devices or top_devices) lives in the schema, not the description, so an agent gets no exclusion rules from the prose.

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