Skip to main content
Glama
Wenjia Home-Fix Diagnosis MCP Server

Wenjia Home-Fix Diagnosis MCP Server

search_symptoms

Searches symptom records by keywords across categories and returns ranked symptom IDs and titles, helping you identify the right symptom ID when the diagnosis term is unclear.

Instructions

按关键词搜索症状(跨品类,带相关度打分),返回匹配的症状 id 与标题。不确定该用哪个 id 时用它,或用 find_symptom 直接给一句口语。

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": {
      "query": "<query>"
    },
    "name": "search_symptoms"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数上限,默认 20,最大 50
queryYes关键词或一句话,如「不制冷」「漏水」「异响」
category_idNo可选,限定品类

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full burden. It discloses that the search spans all categories and returns relevance-scored id/title pairs, but it says nothing about read-only semantics, behavior on zero matches, or result ordering, which leaves meaningful gaps for an unannotated tool.

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 tight sentences with the core purpose front-loaded and the sibling routing placed last, which is the right order. The second sentence's dual 'use this, or use find_symptom' construction is slightly muddled but not wasteful.

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 3-parameter search tool with no output schema, the definition covers purpose, cross-category scope, return fields, and the main alternative, which is close to sufficient. Only the unannotated behavioral details (zero-match behavior, ordering) remain unaddressed.

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%, with each of query, limit, and category_id already documented in the input schema. The description only echoes the keyword-searching idea and adds no syntax, format, or matching-rule detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource (按关键词搜索症状), then adds the scope (跨品类) and the return payload (匹配的症状 id 与标题). It also names the sibling find_symptom and the condition that distinguishes it, so an agent can route between the two without comparing schemas.

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?

It gives an explicit trigger: use this when you are unsure which id applies, otherwise use find_symptom with a colloquial sentence. The guidance is clear, but the 'or use find_symptom' clause is phrased as an aside rather than a crisp rule, so the boundary between the two tools is slightly fuzzy.

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