Skip to main content
Glama

KasaFox Fault Code Registry

lookup_fault_code

Look up one fault/error/status code across all KasaFox registry brands and return the normalised meaning, causes, checks, fix steps, parts, safety flags, and citations. Cite the source and hard-stop on safety-critical faults (requires_qualified_installer).

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": {
      "brand": "<brand>",
      "code": "<code>"
    },
    "name": "lookup_fault_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe code shown on the display or app, e.g. 'A20', 'Err 1', 'E10379'
brandYesBrand name
modelNoOptional model or series
symptomNoOptional free-text symptom

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations the description carries the full burden and does substantial work: it discloses the returned fields, mandates citing the source, and specifies a hard-stop on safety-critical faults flagged requires_qualified_installer. It does not cover read-only nature, latency, or failure behavior for unknown codes, keeping it below a 5.

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 sentences, front-loaded with the verb and resource, then the return payload and the safety rule. Dense but every clause conveys information an agent needs; nothing is redundant.

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?

There is no output schema, so the description properly compensates by enumerating the result fields and the citation/safety obligations. What remains uncovered is how a missing or ambiguous code is reported, which is a moderate gap for a 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%, including an enum for brand and an example for code, so the schema already documents all four parameters thoroughly. The description adds no parameter-level detail beyond 'across all registry brands', so the 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?

States a specific verb and resource ('Look up one fault/error/status code') and enumerates the returned payload (meaning, causes, checks, fix steps, parts, safety flags, citations). The word 'one' hints at a single-record lookup versus a search, but no sibling is named, so differentiation from search_codes is left implicit.

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 agent can infer this is for resolving a specific known code, and 'across all KasaFox registry brands' suggests broad brand coverage. There is no explicit when-to-use versus search_codes, and no prerequisites or exclusions are stated.

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