Skip to main content
Glama

repairinfo: repairability of devices

Best devices in a category

top_devices
Read-onlyIdempotent

The most repairable and durable devices of a category, sorted by score. Optional filters: minimum guaranteed update years, user-replaceable battery, brand. Use this for questions like "which phone gets updates the longest" or "which tablets have a replaceable battery".

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": {
      "category": "<category>"
    },
    "name": "top_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNo
limitNo
categoryYes
min_update_yearsNo
replaceable_batteryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover the safety profile: read-only, idempotent, non-destructive, and closed-world. The description adds useful context about ranking by score and optional filter semantics, but it does not explain result format, limit truncation behavior, or how the score is composed.

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 is two tight sentences: the first states purpose and ranking, and the second provides filters plus example usage. Every sentence contributes useful information without repetition.

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

Completeness3/5

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

The tool has five parameters, no output schema, and no schema descriptions, so the description must carry more explanatory burden. It covers purpose, examples, and most filters, but omits limit semantics and return-value details, leaving the definition adequate but incomplete.

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?

With 0% schema description coverage, the description partially compensates by naming the brand, minimum update years, and replaceable battery filters and implying the required category. However, it never explains the limit parameter or the category enum values, so important parameter meaning is left to the schema.

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 states that the tool returns the most repairable and durable devices of a category, sorted by score, which is a clear resource and ranking purpose. It does not explicitly distinguish itself from sibling tools such as search_devices, so it falls short of a 5.

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?

The description gives concrete example questions ('which phone gets updates the longest', 'which tablets have a replaceable battery') that clearly indicate when to use the tool. It does not state when not to use it or name an alternative for general device searching, so a 4 is appropriate.

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