Skip to main content
Glama

repairinfo: repairability of devices

Search devices

search_devices
Read-onlyIdempotent

Search smartphones, tablets, laptops, TVs, washing machines, dishwashers and vacuum cleaners by brand, sales name or model number. Returns repairability and durability score, EU repairability class, guaranteed update years 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": {
      "query": "<query>"
    },
    "name": "search_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesBrand, sales name or model number, e.g. "Galaxy S26" or "SM-S942B"
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value by naming the returned fields (repairability score, durability score, EU repairability class, guaranteed update years, device link), which matters because no output schema exists. It stops short of describing ordering, pagination or empty-result behavior.

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 dense sentences, front-loaded with the search capability and followed by return values; no filler. The long category list is informative rather than redundant, though it consumes space without mentioning the category filter explicitly.

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 simple read-only search tool with no output schema, the description covers what can be queried and what is returned, which is most of what an agent needs. The remaining gap is result-size behavior (limit semantics, max results, empty results), which is left to the schema's minimum/maximum alone.

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% — the query parameter is documented in the schema, but category and limit are not. The description's category enumeration maps onto the category enum and helps, but the limit parameter (default 8, max 20) is never explained, so the description only partially compensates for the coverage gap.

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?

States a specific verb (Search) plus the resource and the searchable fields (brand, sales name, model number), and enumerates the device categories covered, so the scope is unambiguous. It does not distinguish itself from siblings like get_device or lookup_barcode, so an agent must infer the boundary itself.

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 rather than stated: the description tells you what can be searched and what comes back, which suggests using it for exploratory/discovery queries. There is no explicit when-to-use vs. get_device/lookup_barcode guidance and no exclusion or no-result 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