Skip to main content
Glama

project_find

Find blocks in Loxone Config projects by title, description, type, room, category, or page to locate logic elements for inspection or safe edits.

Instructions

Searches blocks by title/description, type, room, category or page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "project_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
roomNo
typeNo
limitNo
queryNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, no output schema, and 0% schema description coverage, the description carries the full disclosure burden and mostly drops it. It never says what a result looks like, whether matching is exact or fuzzy, how multiple filters interact, or what the default limit of 50 implies for truncation.

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 front-loaded sentence with no filler, and the resource and facets come first. It is efficient rather than padded, though the brevity comes at the cost of the behavioral detail noted elsewhere.

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?

For a 6-parameter search tool with zero annotation coverage, no documented schema, and no output schema, the description is far too thin. An agent could invoke it, but could not predict result shape, filter interaction, or truncation behavior.

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 0%, so description must compensate; it does partially by clarifying that "query" matches title/description and naming page, room, type, and category as filter axes. However, the limit parameter is never mentioned, and no parameter is given format expectations or value examples, leaving real gaps.

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 supplies a specific verb ("searches") and resource ("blocks") and enumerates the searchable facets, which the bare name project_find does not convey. It is clear on its own, but it draws no boundary against siblings such as project_get_block or project_list_pages, so an agent must still infer which one to reach for.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this rather than project_get_block, project_list_pages, or project_text, and no mention of alternatives or prerequisites. Nothing tells the agent whether filters are combined (AND) or interchangeable, which is exactly the ambiguity a search tool must resolve.

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