Skip to main content
Glama

Step-by-step repair guide

repair_guide
Read-onlyIdempotent

Safe step-by-step guides: clean the washing machine pump filter, washing machine not spinning, clean dishwasher filters, replace the fridge door seal, oven not heating (which element fails). Returns steps, time, tools, FAQs and the guide URL.

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": {
      "question": "<question>"
    },
    "name": "repair_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the answer (default: es). Content is in Spanish; translate it if needed.
questionYesWhat the user wants to fix, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish that this is a non-destructive, idempotent, closed-world read, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing the response contents (steps, time estimate, tools, FAQs, guide URL), which tells the agent what it will get back even though no output schema exists.

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?

A single sentence opens with the tool's purpose and immediately fronts the topic catalog, closing with the return payload. The dense comma-separated list is efficient, though it reads more like a content index than prose and could be marginally tighter.

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 two-parameter read tool with no output schema, disclosing the return fields is the right move and is done. However, the `question` field accepts arbitrary free text and the description never states what happens when the question falls outside the five listed topics, nor whether Spanish content is automatically translated, which leaves a real behavioral gap.

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%, with the `question` parameter documented as free-form user phrasing (max 300 chars) and `language` enumerating es/en with a default. The description adds no syntax or formatting guidance beyond that, so the schema carries the load; the topic list only loosely hints at valid `question` values.

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 resource (step-by-step repair guides) and enumerates the exact topics covered: pump filter cleaning, spinning faults, dishwasher filters, fridge door seals, and oven heating elements. It is clear what the tool returns, but it does not contrast itself with siblings such as diagnose_error_code or answer_library, so the agent must infer the boundary.

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?

There is no explicit when-to-use or when-not-to-use statement, but the closed topic list implies scope: the tool is appropriate for those five household-appliance repairs. Nothing tells the agent what to do for an error code or a warranty question, where a sibling tool is likely the better fit.

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