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

Wenjia Home-Fix Diagnosis MCP Server

price_band

Returns the CNY home-repair price range for a described symptom, answering roughly how much a fix will cost.

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": "price_band"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo用户原话,例如「空调开一晚上房间还是不凉」。推荐直接给这一句:不传 category_id 和 symptom_id 时,必须给我。
symptom_idNo
category_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.4
    • changedInput schema / properties / query / description
      Previous value: -"可选:口语描述,省略 id 时用它定位"New value: +"用户原话,例如「空调开一晚上房间还是不凉」。推荐直接给这一句:不传 category_id 和 symptom_id 时,必须给我。"
  2. First observedv0.2.3

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose that the result is a price range in RMB for an on-site (上门) repair, which is useful return-shape context, but it says nothing about whether pricing varies by region, whether results are cached/estimated, or whether a prior symptom lookup is needed.

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 compact sentences, scope stated first and the disambiguating constraint second. Nothing is redundant or padded.

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?

Return type is roughly conveyed (price range, RMB) and no output schema exists, so that part is adequate. But with three parameters, two of them undocumented and no annotations at all, the definition leaves an agent guessing about inputs and about preconditions for calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: query is documented in the schema, but symptom_id and category_id have no description anywhere. The prose says 'a symptom' but never explains the ID parameters, their relationship to query, or which takes precedence — a real gap the description should have closed.

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 names a specific verb and resource (retrieving the on-site repair price band for a symptom) and pins the currency (RMB). The scoping sentence 「只回答问题『修这个大概多少钱』」 makes clear it is a cost-estimate tool and not a diagnosis or a fix plan, which is enough to separate it from siblings even without naming them.

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?

The 'only answers the question X' clause effectively defines the trigger condition: use it for cost questions and not for diagnosis or repair steps. It stops short of naming an alternative tool or stating prerequisites (e.g., whether a symptom must first be identified).

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