Skip to main content
Glama
Device Specs MCP Server

Device Specs MCP Server

by GranTurismo

List phones by chipset

list_phones_by_chipset
Read-onlyIdempotent

Find phones powered by a specified system-on-chip by matching the exact catalog chipset name; paginate results and choose compact output.

Instructions

List phones powered by a given system-on-chip. The chipset must match the catalog string exactly (case-insensitive), e.g. 'Google Tensor G4', 'Apple A17 Pro', 'Qualcomm SM8650-AC Snapdragon 8 Gen 3', 'Mediatek Dimensity 9300'. If you only know part of the name, use search_phones with {"chipset_contains":"Snapdragon 8 Gen 3"} instead.

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": {
      "chipset": "<chipset>"
    },
    "name": "list_phones_by_chipset"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of phones to return (1-200, default 50).
offsetNoNumber of phones to skip, for paging through large result sets.
chipsetYesFull chipset name as it appears in the catalog, e.g. 'Google Tensor G4'.
compactNotrue (default) returns a short projection of ~20 key fields per phone to save tokens; false returns the full raw API JSON.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered; the description adds the non-obvious matching rule (exact, case-insensitive catalog string) that determines whether results come back empty. It does not describe result ordering or empty-result behavior, which is a modest remaining gap for a read tool.

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?

Three short sentences: purpose first, matching rule second, alternative routing last. No filler, and the constraint an agent is most likely to violate (partial names) 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?

For a simple filtered-list tool with full schema coverage and annotations carrying the safety profile, this is nearly complete; paging and result projection are handled by the schema. Minor gaps remain around ordering and what an empty result means, but nothing blocks a correct call.

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 all four parameters are documented in structured form and the baseline is 3. The description still adds value by clarifying that chipset is a case-insensitive exact catalog string rather than a free-text query, which the schema's 'full chipset name' phrasing only implies.

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?

States a specific verb and resource ('List phones powered by a given system-on-chip') and immediately pins the scope to exact chipset matching, which is what separates it from the fuzzy search sibling. An agent can distinguish it from search_phones without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative and the condition that selects it: use search_phones with {"chipset_contains": ...} when only part of the name is known. It also supplies concrete example values so the agent can self-check whether its input is exact.

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