Skip to main content
Glama

Check compatibility

check_compatibility
Read-onlyIdempotent

Checks whether a device works with an assistant/ecosystem (Alexa, Google Home, Apple Home, Home Assistant, SmartThings) or with another device or hub, how (native, via Matter, through the brand's hub) and what hub or Thread border router is needed. Also explains Matter, Thread, Zigbee, Z-Wave, Wi-Fi and Bluetooth, and which devices act as Matter controller / Thread border router in each ecosystem. Only manufacturer-confirmed facts, with sources.

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": {
      "device": "<device>"
    },
    "name": "check_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceYesThe device or protocol, e.g. «Nuki Smart Lock Pro», «Aqara sensor puerta P2», «Philips Hue», «Matter», «Zigbee».
languageNoLanguage of the answer (default: es). Content is in Spanish; translate it if needed.
works_withNoThe ecosystem or the other device/hub, e.g. «Apple Home», «Alexa», «HomePod mini», «Home Assistant».

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a read-only, idempotent, closed-world lookup, so the baseline is low. The description adds meaningful context beyond that: answers are restricted to manufacturer-confirmed facts and come with sources, and it discloses the shape of the answer (compatibility mechanism plus the required hub or border router). It does not mention response length, latency, or what happens when a device is unknown.

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?

Two sentences, front-loaded with the compatibility check before the protocol-education addendum. The second sentence is somewhat sprawling and mixes in tangential scope, but every clause still describes real capability rather than restating 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?

For a three-parameter, read-only lookup with no output schema, the description is nearly sufficient: it covers the answer's dimensions (works or not, mechanism, required hub) and the sourcing guarantee. The main gap is that it never says how an unsupported or unknown device is reported, which matters for a factual lookup tool.

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 each parameter is already documented with examples and an enum for language, so the schema carries the burden. The description adds only marginal meaning, notably that protocols themselves (Matter, Zigbee) are valid device values, which the schema examples already show. 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 gives a specific verb (checks) and a precisely scoped resource: device-to-ecosystem/hub compatibility, including the mechanism (native, Matter, brand hub) and required hardware. It also states a secondary educational scope (protocol explanations, Matter controller / Thread border router roles). The purpose is clear without opening the schema, though it never names or contrasts a specific sibling such as recommend_smart_home_products.

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 only implied: the pairing of a device plus an optional works_with naturally maps to a 'does X work with Y' question. There is no explicit when-to-use or when-not guidance, and no routing to siblings such as recommend_smart_home_products for buying advice or setup_guide for configuration steps.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources