Skip to main content
Glama
Device Specs MCP Server

Device Specs MCP Server

by GranTurismo

Identify a phone from its model number

lookup_model_number
Read-onlyIdempotent

Resolve a hardware model or variant code to its marketing name, manufacturer, chipset, and full specification sheet when found.

Instructions

Resolve a hardware model/variant code (the string printed on the device or returned by Android's Build.MODEL, e.g. 'SM-S928B', 'A3106', 'GP8GD', '2201116SG', 'TA-1004') to its marketing name, manufacturer and chipset, and return the full specification sheet when found.

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": {
      "model_number": "<model_number>"
    },
    "name": "lookup_model_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
model_numberYesHardware model number or variant code, e.g. SM-S928B.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral information: what is returned (marketing name, manufacturer, chipset, full spec sheet) and the conditional 'when found', which flags that a lookup can miss. It leaves the not-found behavior and any external API dependency implicit.

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?

A single sentence that leads with the verb and input type, then lists outputs. The five inline examples cost length but earn it by pinning down the expected input format across vendors. No filler or restatement of the title.

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 carries the burden of explaining returns, and it does: marketing name, manufacturer, chipset, and the full spec sheet. For a simple two-parameter read-only lookup this is close to sufficient; the only real gap is how a non-match is surfaced to the caller.

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 parameters are documented in the schema, including the compact flag's false-vs-true behavior and default. The description adds only example values for model_number (already echoed in the schema example) and says nothing about compact, so it does not add meaning beyond the structured data. Baseline 3 applies.

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 uses a specific verb ('Resolve') and a precisely bounded resource ('hardware model/variant code'), and gives five concrete example codes so the agent knows exactly what input shape belongs here. It implicitly separates itself from siblings like get_phone_specs or search_phones by requiring a model code rather than a name or query, but it never names an alternative, so the differentiation is inferred rather than stated.

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?

It gives a clear triggering context: the string printed on the device or returned by Android's Build.MODEL. That tells the agent when this tool applies. It stops short of exclusions or named alternatives, so an agent facing a marketing name instead of a code gets no explicit routing advice.

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