Skip to main content
Glama

Step-by-step smart home guide

setup_guide
Read-onlyIdempotent

Step-by-step guides: build a smart home from scratch, a second home or empty house watched without fees, smoke/CO/water detectors, saving on heating with smart radiator valves, moving to Matter, safety for older people living alone, and smart home for a tourist flat. Returns steps, FAQs, safety notes (electrician when wiring), suggested products and sources.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the description's job is to add context beyond that — and it does by declaring the response shape (steps, FAQs, safety notes, suggested products, sources) and flagging that wiring steps call for an electrician. It adds no note on guide length, freshness, or how narrowly the question must match a covered topic, which keeps it below a 5.

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?

It is a single front-loaded sentence led by the tool's role, then its topic coverage, then its return contents — no filler and no repetition of the name or title. The topic enumeration is long and slightly list-heavy, but each entry does real routing work by telling the agent which user intents are in scope.

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 two-parameter read-only lookup with no output schema, the description covers both what goes in (a user-phrased setup question) and what comes back (steps, FAQs, safety notes, products, sources), plus the safety caveat. The only meaningful gap is the absence of explicit routing against siblings with adjacent scope.

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%: the schema already documents 'question' as the user's own words with a 300-character cap, and 'language' with its enum and default. The description adds no further guidance on phrasing the question or on how broad versus specific queries behave, so the baseline 3 for a fully documented schema 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 clearly identifies this as a retrieval tool for step-by-step smart home guides and enumerates the concrete scenarios covered (from-scratch build, second home, detectors, radiator valves, Matter migration, elderly safety, tourist flat). An agent can tell it returns procedural guidance rather than product recommendations or compatibility data. It does not explicitly distinguish itself from the similarly-scoped answer_library sibling, so it falls short of a 5.

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?

The topic list implicitly signals when to reach for this tool — when the user wants a full setup walkthrough on one of those scenarios. There is no explicit when-not guidance and no named alternative (e.g. answer_library for single factual questions, recommend_smart_home_products for purchase lists), leaving the agent to infer the boundary from topic overlap alone.

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