Skip to main content
Glama

icon_find

Search the Loxone icon library by name or German keyword to retrieve icon names and UUIDs for state_add. Use it to find the right icon before configuring states.

Instructions

Searches the Loxone icon library by name or keyword (German keywords work best), e.g. 'sonne', 'regen', 'thermometer'. Returns name and UUID for state_add.

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose the return shape ('name and UUID'), which matters since there is no output schema, plus a search-quality hint about German keywords. It omits matching semantics — substring vs fuzzy, case sensitivity, result limits, and empty-result behavior — which are the traits an agent would need to use the result reliably.

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 short sentences with zero filler: the core action and query semantics come first, the return contract second. Every clause earns its place, including the examples and the pointer to state_add.

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 one-parameter lookup with no output schema, the definition covers the essentials: what is searched, how to phrase the query, and what comes back. The only meaningful gap is the absence of matching/limit behavior, which is minor for a simple search helper compared with the gaps in most sibling definitions.

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

Parameters4/5

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

Schema coverage is 0% and the single parameter is a bare 'query' string, so the description must compensate. It does so meaningfully by specifying that the value is a name or keyword, giving three worked examples, and noting that German terms perform best — enough to shape a correct call, though it says nothing about multi-word or partial-term behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Searches the Loxone icon library by name or keyword,' with concrete query examples ('sonne', 'regen', 'thermometer'). It also names the downstream consumer (state_add), so an agent can tell exactly what this tool is for and where its output goes, without opening the schema.

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 description makes the use case clear (look up icons before adding state icons) and gives a practical hint that German keywords work best, which directly affects how to phrase the query. It stops short of stating when-not to use it or what to do on empty results, but no sibling performs icon lookup, so there is no real alternative to route away from.

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