Skip to main content
Glama
Device Specs MCP Server

Device Specs MCP Server

by GranTurismo

Compare phones side by side

compare_phones
Read-onlyIdempotent

Compare two to four phones side by side and return key specs plus a differences map showing only fields that vary, answering X vs Y questions.

Instructions

Fetch two to four phones and return their key specs side by side plus a 'differences' map containing only the fields whose values differ, which is the quickest way to answer 'X vs Y' questions. Each phone is given as manufacturer + model in catalog spelling.

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": {
      "phones": "<phones>"
    },
    "name": "compare_phones"
  }
}

Input Schema

NameRequiredDescriptionDefault
phonesYesTwo to four phones to compare.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already carry readOnly, idempotent, non-destructive and open-world hints, so the safety profile is covered. The description adds valuable non-annotation detail: the result includes side-by-side specs plus a differences map containing only differing fields, and inputs must use catalog spelling. It omits failure behavior for unknown models.

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?

Two tight sentences with no filler: the first states what is fetched and returned plus the use case, the second states the input format. The most decision-relevant information is front-loaded.

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?

With no output schema, the description usefully characterizes the return value and the input spelling constraint. Minor gaps remain: 'key specs' is unspecified, and there is no mention of what happens when a model is not found or how large the response may be.

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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by imposing a real constraint the schema does not — each phone must be supplied as manufacturer + model in catalog spelling, which affects lookup success.

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?

Uses a specific verb and resource ('Fetch two to four phones and return their key specs side by side') and defines the exact output shape, including the 'differences' map. The two-to-four scope plus per-phone manufacturer+model input clearly separates it from single-phone tools like get_phone_specs or list-based siblings.

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?

Explicitly frames the intended use case as answering 'X vs Y' questions, telling the agent when this tool is the right pick. It stops short of naming alternatives or stating when not to use it (e.g., for a single phone's full specs), so it is clear but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.