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

Wenjia Home-Fix Diagnosis MCP Server

by gmcho2009-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_category

Retrieves the complete symptom list for a home appliance category, with one-line summaries, to help expand from a category or confirm which faults it covers.

Instructions

取某品类的全部症状清单（每个症状一句话摘要）。用于从品类入口展开，或确认「这个品类管哪些故障」。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo品类中文名，如「洗衣机」，category_id 的替代写法
category_idNo品类 id，如 washing_machine；也可传品类中文名

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A3.8/5.0
Behavior3/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. It discloses the return shape (all symptoms, one-sentence summaries), but it does not mention permissions, pagination, ordering, or error behavior.

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 with no wasted wording: the first states what is returned, and the second states when to use it. The information is front-loaded and easy to scan.

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 simple read tool with no output schema, the description explains the return content and the primary usage contexts. Minor gaps remain around pagination, limits, and how to handle the case where neither category nor category_id is supplied, but the core calling information is present.

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 schema already explains category and category_id, including that the Chinese category name can substitute for the id. The description adds no parameter meaning beyond the schema, so the baseline of 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 states a specific verb and resource: get the complete symptom list for a category, with each symptom summarized in one sentence. It clearly conveys the scope, though it does not explicitly name sibling tools such as get_symptom or list_categories.

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 concrete usage contexts: expanding from a category entry or confirming which faults a category covers. It does not state when not to use it or explicitly point to alternatives, so it stops short of full routing guidance.

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

Deploy Server

Other Tools