Skip to main content
Glama

Nido Raíz — Inmuebles en Colombia

Ver la ficha de un inmueble

ver_inmueble
Read-onlyIdempotent

Devuelve la ficha completa de un inmueble: descripción, administración, áreas, año, parqueaderos, y los enlaces a la ficha web y al recorrido virtual si lo tiene. Usa el "codigo" que devuelve buscar_inmuebles.

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>"
    },
    "name": "ver_inmueble"
  }
}

Input Schema

NameRequiredDescriptionDefault
codigoYesEl "codigo" de un resultado de buscar_inmuebles, o el código del inmueble que la persona leyó en un aviso o en la ficha (dos letras y cinco caracteres, como GP00017)

Output Schema

NameRequiredDescriptionDefault
inmuebleYes
inmobiliariaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds that the record may include web/virtual-tour links, but says nothing about failure behavior when a code doesn't exist or whether results are cached. With rich annotations, a 3 is appropriate.

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 sentences, front-loaded with the purpose and the returned content, then the input convention. No filler or redundant phrasing.

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 values needn't be explained, and the annotations cover safety semantics. The only real gap is the absence of any note on what happens with an invalid or unknown código, which would help an agent recover from errors.

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 100% and the schema already documents "codigo" including its two-letter-plus-five-character format and the example GP00017. The description's sentence about using the code from buscar_inmuebles largely restates the schema, so the baseline 3 applies.

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 ("Devuelve la ficha completa de un inmueble") and enumerates the fields the record contains: descripción, administración, áreas, año, parqueaderos, plus links to the web page and virtual tour. That is clearly the detail-fetch counterpart to the search sibling buscar_inmuebles, not a listing tool.

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?

Explicitly ties invocation to a prior search by saying to use the "codigo" that buscar_inmuebles returns, which establishes the search-then-detail workflow. It doesn't state when NOT to use it or mention the other siblings (agendar_visita, evaluar_inversion), but the context of use is clear enough.

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