Skip to main content
Glama

Objelio Immobiliensuche

Explain search criteria

explain_criteria
Read-onlyIdempotent

Use this when the user wants to check how a property search request is understood before searching. Shows the request as structured criteria the user can check and correct. The text is processed by an AI service (Anthropic API) to extract the criteria; Objelio does not link it to a person. Does not search.

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": {
      "text": "<text>"
    },
    "name": "explain_criteria"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe user's request in their own words.

Output Schema

NameRequiredDescriptionDefault
hinweisYes
in_wortenYesThe criteria in German words.
kriterienYesStructured criteria, can be passed as criteria to search_listings (leave out null and empty fields).
nicht_beruecksichtigtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious context: the text is sent to a third-party AI service (Anthropic API) and is not linked to a person, which is privacy information an agent cannot get from 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?

Four short sentences, front-loaded with the usage trigger, then behavior, then privacy, then the negative constraint. No filler; the only mild redundancy is restating 'request as structured criteria' after the opening clause.

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?

An output schema exists, so return shape need not be explained, and the single parameter is fully documented. The description covers the privacy and non-searching behavior an agent needs; it could add what happens when the text yields incomplete criteria, but nothing essential is missing.

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?

There is a single parameter with 100% schema description coverage ('The user's request in their own words', 1–500 chars), so the schema already carries the meaning. The description adds only the implicit framing that this text is the input to be parsed, which mirrors the schema wording rather than extending it.

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?

The description gives a specific verb and resource — shows a property search request as structured criteria for the user to check and correct — and explicitly negates the neighboring capability with 'Does not search,' which separates it from search_listings without opening either 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?

'Use this when the user wants to check how a property search request is understood before searching' gives a clear trigger condition, and 'Does not search' rules out using it as the actual search. It stops short of naming search_listings as the follow-up tool, so routing still requires a small inference.

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