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

Wenjia Home-Fix Diagnosis MCP Server

Related Servers

Alternatives to Wenjia Home-Fix Diagnosis MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables users to diagnose home appliance errors and receive safety actions by identifying products from photos or error codes, using official manufacturer data.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with manufacturer-sourced HVAC technical documentation, enabling error-code lookup, diagnostics, and guided troubleshooting with exact source citations.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables turning spoken household issues into evidence-linked maintenance cases, deterministic diagnostic plans, quote comparisons, and owner-approved but unexecuted action proposals.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Alexa+ and other MCP clients to diagnose household appliance problems through safety-reviewed triage steps, find model-fit parts, place explicitly confirmed orders, and schedule delivery follow-ups and preventive maintenance. Every case, order, and reminder persists per household, so conversations resume from any device days later.
      MIT

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation3/5

    There are effectively two overlapping clusters: three symptom-finding entry points (diagnose, find_symptom, search_symptoms) and three overlapping views of the same diagnostic tree (get_symptom superset of fix_plan superset of cause_ranking). The descriptions do a good job of stating 'use me when / don't use me' boundaries and explicitly route between them, so an agent can usually recover, but the boundaries are decided by the user's phrasing rather than by a distinct resource, which is a misselection hazard.

    Naming Consistency3/5

    Mostly readable verb_noun names (list_categories, get_category, get_symptom, search_symptoms, find_symptom) but the other half are bare noun/adjective phrases (price_band, fix_plan, cause_ranking, stop_check) or an unqualified verb (diagnose). Worse, two near-identical actions use different verbs — search_symptoms vs find_symptom — which weakens the naming signal exactly where disambiguation is already thin.

    Tool Count4/5

    Ten tools is a well-scoped size for a diagnostic knowledge base, and the token-efficiency split (cause_ranking < fix_plan < get_symptom) is a defensible design. It is slightly padded, though: three retrieval entry points and three overlapping detail views mean at least one or two tools could be collapsed without losing capability.

    Completeness4/5

    The lifecycle is well covered: browse categories, list symptoms, search/find by natural language, triage from vague complaints, ranked causes, full repair steps with parts, price bands, and a mandatory safety gate. Minor gaps remain — no parts/accessory lookup as a first-class query, no flat cross-category symptom listing, and no way to go from cause back to candidate symptoms — but an agent can work around these via search and get_symptom.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues