Skip to main content
Glama
Device Specs MCP Server

Device Specs MCP Server

by GranTurismo

Get phone specifications

get_phone_specs
Read-onlyIdempotent

Look up a single smartphone's full specification sheet by manufacturer and model, covering display, chipset, RAM, battery, cameras, connectivity, dimensions, and launch prices.

Instructions

Return the specification sheet for one smartphone by manufacturer and model name. Includes display (size, panel, refresh rate, brightness), chipset/CPU/GPU, RAM and storage options, battery capacity and charging, cameras, dimensions and weight, IP rating, connectivity (NFC, Bluetooth, USB, Wi-Fi), sound, benchmark scores, EU energy label, launch prices, colours and hardware model numbers. Model names follow catalog spelling, e.g. manufacturer='Samsung' model='Galaxy S24 Ultra', manufacturer='Apple' model='iPhone 15 Pro', manufacturer='Google' model='Pixel 9 Pro'.

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": {
      "manufacturer": "<manufacturer>",
      "model": "<model>"
    },
    "name": "get_phone_specs"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesModel name as marketed, without the brand, e.g. 'Galaxy S24 Ultra', 'iPhone 15 Pro', 'Pixel 9 Pro', 'Redmi Note 13 Pro+'.
compactNofalse (default) returns the full raw API JSON (raw spec strings, cameras, sensors, variants, normalized_specs); true returns a short projection of ~20 key fields.
manufacturerYesBrand name, e.g. Samsung, Apple, Google, Xiaomi, OnePlus, vivo, Oppo, Motorola, Sony, Nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false and openWorld=true, so the safety profile is covered; the description adds real value by detailing exactly what the payload contains (benchmarks, EU energy label, launch prices, hardware model numbers) and by warning that model names must follow catalog spelling. It stops short of describing failure behavior when no match is found.

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?

Front-loaded with the core action in the first sentence, followed by the returned-fields inventory and naming examples. The field enumeration is long but each item tells the agent something about coverage that could affect the decision to call; no filler or marketing language.

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 available, the description carries the burden of describing returns and does so thoroughly, and it establishes the naming convention needed for a successful call. The main remaining gap is not mentioning the compact short-projection mode or error/ambiguity handling, which matter for agent retry logic.

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 description coverage is 100% and both manufacturer and model already carry examples in the schema, so the description's manufacturer/model examples are largely duplicative. The compact flag, which materially changes the response shape, is explained only in the schema and never referenced in the description.

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 and resource: 'Return the specification sheet for one smartphone by manufacturer and model name,' then enumerates the returned domains so an agent knows it is a full-spec lookup rather than a search. It implicitly separates itself from search_phones/list_phones_by_manufacturer by requiring a single exact model, though no sibling is named explicitly.

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: you supply a manufacturer and a model name that follows catalog spelling, and the worked examples (Samsung/Galaxy S24 Ultra, Apple/iPhone 15 Pro, Google/Pixel 9 Pro) show the expected format. There is no explicit when-to-use vs. when-to-use-a-sibling statement and no guidance on what to do when a model name is ambiguous or absent.

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