Skip to main content
Glama

Objelio Immobiliensuche

Get search alert link

get_search_alert_link
Read-onlyIdempotent

Read-only. Returns a link to a page on objelio.de where the user can subscribe to e-mail alerts for these criteria: new matching listings and price reductions, at most one e-mail a day, unsubscribe with one click. Pass the same criteria as in search_listings (at least one, e.g. a location). The user enters the e-mail address on that page and confirms it by e-mail; do not ask for it in the chat. Nothing is saved until the user does so.

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": {
      "criteria": "<criteria>"
    },
    "name": "get_search_alert_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
criteriaYesStructured search criteria, as in search_listings.

Output Schema

NameRequiredDescriptionDefault
linkYesPage on objelio.de where the user enters an e-mail address and confirms it. Show it to the user.
hinweisYes
kriterienYesThe saved criteria in German words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / criteria / properties / features_preferred / items / enum
      Previous value: -[
      -  "balkon",
      -  "terrasse",
      -  "garten",
      -  "aufzug",
      -  "keller",
      -  "einbaukueche",
      -  "gaeste_wc",
      -  "barrierefrei",
      -  "stellplatz",
      -  "pool"
      -]New value: +[
      +  "balkon",
      +  "terrasse",
      +  "garten",
      +  "aufzug",
      +  "keller",
      +  "einbaukueche",
      +  "gaeste_wc",
      +  "barrierefrei",
      +  "stellplatz",
      +  "pool",
      +  "sauna",
      +  "kamin",
      +  "wintergarten",
      +  "einliegerwohnung",
      +  "fussbodenheizung",
      +  "photovoltaik",
      +  "waermepumpe",
      +  "wallbox",
      +  "glasfaser",
      +  "klimaanlage"
      +]
    • changedInput schema / properties / criteria / properties / features_required / items / enum
      Previous value: -[
      -  "balkon",
      -  "terrasse",
      -  "garten",
      -  "aufzug",
      -  "keller",
      -  "einbaukueche",
      -  "gaeste_wc",
      -  "barrierefrei",
      -  "stellplatz",
      -  "pool"
      -]New value: +[
      +  "balkon",
      +  "terrasse",
      +  "garten",
      +  "aufzug",
      +  "keller",
      +  "einbaukueche",
      +  "gaeste_wc",
      +  "barrierefrei",
      +  "stellplatz",
      +  "pool",
      +  "sauna",
      +  "kamin",
      +  "wintergarten",
      +  "einliegerwohnung",
      +  "fussbodenheizung",
      +  "photovoltaik",
      +  "waermepumpe",
      +  "wallbox",
      +  "glasfaser",
      +  "klimaanlage"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / criteria / properties / features_preferred / items / enum
      Previous value: -[
      -  "balkon",
      -  "terrasse",
      -  "garten",
      -  "aufzug",
      -  "keller",
      -  "einbaukueche",
      -  "gaeste_wc",
      -  "barrierefrei",
      -  "stellplatz"
      -]New value: +[
      +  "balkon",
      +  "terrasse",
      +  "garten",
      +  "aufzug",
      +  "keller",
      +  "einbaukueche",
      +  "gaeste_wc",
      +  "barrierefrei",
      +  "stellplatz",
      +  "pool"
      +]
    • changedInput schema / properties / criteria / properties / features_required / items / enum
      Previous value: -[
      -  "balkon",
      -  "terrasse",
      -  "garten",
      -  "aufzug",
      -  "keller",
      -  "einbaukueche",
      -  "gaeste_wc",
      -  "barrierefrei",
      -  "stellplatz"
      -]New value: +[
      +  "balkon",
      +  "terrasse",
      +  "garten",
      +  "aufzug",
      +  "keller",
      +  "einbaukueche",
      +  "gaeste_wc",
      +  "barrierefrei",
      +  "stellplatz",
      +  "pool"
      +]
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, yet the description still adds substantial behavioral context: nothing is persisted until the user confirms by e-mail, alerts are capped at one e-mail per day, and unsubscribe is one click. The instruction not to collect the e-mail address in chat is a concrete procedural constraint the annotations cannot express.

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?

The read-only status and the primary outcome are front-loaded, followed by the alert behavior, the invocation rule, and the e-mail hand-off. Every sentence carries operational information, with no restatement of the tool name or filler.

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

Completeness5/5

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

For a single-parameter tool with an output schema already covering the returned link, the description supplies everything else an agent needs: what the link leads to, how to build the criteria, and the complete confirmation flow so the agent does not pollute the conversation with an e-mail request. Nothing relevant is missing.

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 100%, so the nested criteria fields are fully documented in the schema and the baseline is 3. The description goes slightly beyond it by stating the criteria must mirror search_listings and that at least one criterion is required, filling a constraint the schema only weakly enforces through the required-object wrapper.

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?

Names a specific verb and product (returns a link to an objelio.de page where the user subscribes to e-mail alerts) and immediately scopes what the alert covers: new matching listings and price reductions. It is also clearly distinguished from search_listings, whose criteria are reused here rather than re-defined.

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?

Tells the agent exactly how to invoke it (pass the same criteria as search_listings, at least one, e.g. a location) and gives a firm operational rule: the user enters the e-mail address on the page and confirms it there, so the agent must not ask for it in chat. It lacks an explicit 'when not to use this' case, e.g. pointing to search_listings for users who only want to browse.

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