Skip to main content
Glama
Sign In
Fibaro MCP

Fibaro MCP

by ikari-software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

resolve_by_name

Find a device, room, or scene by name. Support plural queries for multiple matches, but errors on ambiguous singular names.

Instructions

Resolve a single device by name (or multiple devices if the query is plural). Errors on ambiguity for singular queries.

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": {
      "query": "<query>"
    },
    "name": "resolve_by_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format: text (default) or json (stringified MCP result)
queryYesName query (e.g., "kitchen light")
kindNoOptional: Restrict kind (device|room|scene). Default: device

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must cover behavior. It mentions the plurality and error behavior, but is silent on side effects, idempotency, or any additional behavioral traits. Minimal disclosure for a tool with no annotations.

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?

The description is a single clear sentence, free of fluff. It conveys core behavior efficiently. Could be slightly longer to cover return value, but overall concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema and the presence of a 'format' parameter, the description should explain what the tool returns and how the format parameter affects it. This is missing, making the tool less complete for an agent to use correctly.

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 coverage is 100%, so each parameter is documented. The description adds context about the query parameter's plurality behavior but does not elaborate further on parameter semantics. Baseline score of 3 is appropriate.

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 states it resolves a device by name, with specific behavior for singular vs plural queries. It distinguishes itself from siblings like find_by_name by mentioning ambiguity handling, but does not explicitly contrast with similar tools.

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 description implies usage context by noting that singular queries error on ambiguity, hinting at when to use carefully. However, it lacks explicit guidance on when to prefer this tool over siblings like find_by_name or the Fibaro-specific tools.

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