Skip to main content
Glama

Nido Raíz — Inmuebles en Colombia

Solicitar una visita a un inmueble

agendar_visita
Destructive

Registra una solicitud de visita a un inmueble y comparte los datos de contacto de la persona con la inmobiliaria dueña, que la llamará para coordinar. SÓLO se puede llamar cuando la persona ha dado su nombre y su teléfono y ha dicho explícitamente que quiere que la contacten. No inventes ni supongas datos de contacto.

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": {
      "codigo": "<codigo>",
      "nombre": "<nombre>",
      "telefono": "<telefono>",
      "consentimiento": "<consentimiento>"
    },
    "name": "agendar_visita"
  }
}

Input Schema

NameRequiredDescriptionDefault
codigoYesEl "codigo" del inmueble que se quiere visitar
correoNoCorreo, si lo dio
nombreYesNombre de la persona interesada
telefonoYesTeléfono de contacto, tal como lo dio la persona
consentimientoYestrue sólo si la persona dijo explícitamente que autoriza que la inmobiliaria la contacte con estos datos
fechaPreferidaNoCuándo le queda bien. Texto libre: "el sábado por la mañana"

Output Schema

NameRequiredDescriptionDefault
mensajeYes
registradaYes
inmobiliariaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations flag destructiveHint=true and openWorldHint=true; the description explains exactly why by disclosing that personal contact data is handed to an external agency that will call the person. It also pins down the consent condition that must hold, which is the crucial behavioral context an agent needs before writing data outward.

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?

Three short sentences with the purpose and external effect first, then the precondition, then the anti-hallucination rule. Every sentence carries a distinct, load-bearing constraint and nothing is repeated from the schema verbatim.

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?

With an output schema present and annotations covering the safety profile, the description covers purpose, consent gating, and external data sharing well. The one notable omission is that idempotentHint=false is never surfaced — an agent is not warned that retrying may create duplicate visit requests.

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 already 100%, so the baseline is 3, but the description adds meaning beyond the schema: it ties nombre and telefono to a real, user-supplied requirement ("No inventes ni supongas datos de contacto") and reinforces that consentimiento is a genuine explicit authorization rather than a defaulted true.

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 ("Registra una solicitud de visita a un inmueble") and adds the consequential side effect ("comparte los datos de contacto ... con la inmobiliaria dueña, que la llamará"). This clearly separates it from browsing siblings such as ver_inmueble or buscar_inmuebles without naming them.

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?

Gives an explicit gate for invocation: only when the person has provided name and phone and has explicitly said they want to be contacted, plus a prohibition on fabricating contact data. It does not name an alternative tool for the case where the user is merely exploring listings, so it stops short of full when/when-not routing.

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