Device Specs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEVICESPECS_API_KEY | Yes | Your RapidAPI key. Required when using the default gateway; without a key the data tools return a clear error with the sign-up link. | |
| DEVICESPECS_API_HOST | No | Value sent in x-rapidapi-host. | deviceultraparser.p.rapidapi.com |
| DEVICESPECS_BASE_URL | No | API gateway base URL. Point it at another host if you self-host or have a direct contract. | https://deviceultraparser.p.rapidapi.com/ |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Device Specs API: normalized hardware specifications for 10,000+ smartphones (Apple, Samsung, Google, Xiaomi, OnePlus, vivo, Oppo, Motorola, Sony, Nothing and 25+ more brands, 1995 to today). Use get_phone_specs when the user names a phone. Use search_phones to find phones by hardware criteria; call list_filter_properties first if unsure which filter keys exist. Model names must match the catalog spelling (e.g. 'Galaxy S24 Ultra', 'iPhone 15 Pro', 'Pixel 9 Pro'); if a lookup returns not_found, try list_phones_by_manufacturer and pick the closest model, or lookup_model_number for codes like SM-S928B. Prices (price_usd) are launch prices and are only known for a subset of phones; 0 or null means unknown.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_phone_specsA | 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'. |
| search_phonesA | Find smartphones matching hardware criteria using the API's filter language: keys are '[_]' and values are strings, numbers or booleans. Operators: (none)=equals, _gt, _gte, _lt, _lte, _contains, _in (comma list), _between ('min,max'), _has. Common properties: manufacturer, model, chipset, ram (GB), storage (GB), battery (mAh), refresh_rate (Hz), displaysize (inches), panel_type, brightness (nits), charging (W), wireless_charging, weight (g), ip_rating, nfc, headphone_jack, card_slot, stereo_speakers, infrared, price_usd, announcedate, android. Example: {"manufacturer":"Samsung","ram_gte":12,"refresh_rate_gte":120,"battery_gte":5000}. All filters are ANDed. Call list_filter_properties for the complete list of properties and aliases. Results come back in catalog order (roughly newest first within a brand). |
| list_phones_by_manufacturerA | List every phone in the catalog from one brand, with key specs for each. Useful to discover exact model names before calling get_phone_specs, or to browse a brand's line-up. Large brands have hundreds of models (Samsung ~1,500), so use limit/offset to page. |
| list_phones_by_chipsetA | 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. |
| lookup_model_numberA | 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. |
| compare_phonesA | 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. |
| list_filter_propertiesA | Return the complete reference for the search_phones filter language: all operators (_gt, _gte, _lt, _lte, _contains, _in, _between, _has), every filterable property with its aliases, type and JSON path, usage notes and worked examples. No network call. Use it before composing a non-trivial search. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| filter-reference | Operators, properties and aliases accepted by the /devices search endpoint, as Markdown. |
TDQS
Scored across 7 tools
Each tool has a distinct retrieval strategy: exact spec lookup, filtered search, brand listing, chipset listing, model-code resolution, and side-by-side comparison. The only real overlap is that search_phones can approximate list_phones_by_manufacturer and list_phones_by_chipset, but the descriptions explicitly route users between them (e.g. pointing to search_phones with chipset_contains when the exact chipset string is unknown). list_filter_properties is a helper for search_phones rather than a competing operation, so confusion risk is low.
All seven names follow a snake_case verb_noun pattern (get_, search_, list_, lookup_, compare_), with list_phones_by_manufacturer and list_phones_by_chipset forming a clean parallel pair. No camelCase or case-mixing anywhere.
Seven tools is well within the ideal 3-15 range and each earns its place: lookup by name, filtered search, two browse axes, code resolution, comparison, and filter reference. Nothing looks like a redundant wrapper.
The surface covers the full read-only lifecycle for a hardware catalog: discovery (search/list), precise retrieval (get_specs), identifier resolution (lookup_model_number), and multi-item comparison, plus documentation of the filter language. Minor gaps remain with no direct enumeration of brands, chipsets, or a paginated full-catalog dump, and compare is capped at four phones, but agents can work around these via search_phones.