Skip to main content
Glama

identifyDevice

Identify a device brand/model from free text for FitsThis compatibility matching. Use before recommending parts.

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": {
      "text": "<text>"
    },
    "name": "identifyDevice"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesUser device description, e.g. Roborock S7 MaxV Ultra

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses very little. It does not say what happens when the free text is unrecognized or ambiguous, whether it returns a canonical brand/model identifier or a confidence level, or whether the call is read-only (implied but unstated).

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?

Two short sentences, zero waste, with the core action front-loaded and the sequencing advice second. Nothing is padded or repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool this is nearly adequate, but with no output schema the description should indicate what the identification yields (e.g. a normalized model name) and how failures surface. Those gaps leave an agent unsure how to consume the result.

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 coverage is 100% and the single text parameter is documented with a concrete example, so the schema does the heavy lifting. The description adds only the framing that the input is free text, which is marginal beyond the schema.

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: identify a device brand/model from free text, plus the domain (FitsThis compatibility matching). It does not explicitly name the sibling it feeds into (findCompatibleParts), but the purpose is unmistakable.

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?

"Use before recommending parts" gives a clear sequencing directive that tells the agent when to invoke it relative to the compatibility flow. It offers no when-not-to guidance or disambiguation from siblings, so it stops short of a 5.

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