Skip to main content
Glama

KasaFox Fault Code Registry

search_codes

Search the registry by code, brand, or title/meaning text and return matching rows with their canonical URLs.

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": {
      "q": "<q>"
    },
    "name": "search_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query: a code (e.g. 'a20'), a brand, or a symptom phrase

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the return shape ('matching rows with their canonical URLs'), which is useful, but says nothing about match semantics (exact vs fuzzy/prefix), case sensitivity, result caps, or pagination — meaningful gaps for a search 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?

One sentence that front-loads the verb, the query modes, and the return value, with no redundant or filler wording.

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 simple one-parameter read-only search with no output schema, the description covers input modes and return payload adequately. It falls short on sibling differentiation and on matching behavior, which an agent needs to decide between this tool and lookup_fault_code.

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 the single parameter q is already documented with examples ('a20', a brand, a symptom phrase). The description merely restates the same three input categories, adding no syntax, formatting, or matching-behavior detail 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 (search) and resource (the registry), and names the three accepted query modes plus what is returned. It does not differentiate itself from the sibling lookup_fault_code, which an agent would likely confuse with a code-based search.

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: 'search by code, brand, or title/meaning text' suggests this is the broad/flexible entry point versus a precise lookup, but the description never says when to prefer lookup_fault_code or list_brands over this tool. No exclusions or prerequisites are given.

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