Skip to main content
Glama

Ver una casa

ver_casa
Read-only

Ficha completa de una casa: descripción, lo que tiene y lo que no, capacidad, precio, verificación y noches ya ocupadas. El id sale de buscar_casas.

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": {
      "casa": "<casa>"
    },
    "name": "ver_casa"
  }
}

Input Schema

NameRequiredDescriptionDefault
casaYes
idiomaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar for the description is lower. The description adds the set of fields the record exposes, which is genuinely useful given there is no output schema, but it says nothing about failure behavior (unknown id), how the id is formatted, or whether all listed sections are always populated.

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 dense sentences with zero filler: the first front-loads the resource and its full content list, the second front-loads the one prerequisite an agent needs. Nothing is repeated from the schema or annotations.

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?

For a simple two-parameter read tool with no output schema, the description covers the returned content and the id source, which is most of what an agent needs. The unresolved gaps are the meaning of `idioma` and what happens with an invalid or unavailable id.

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 description coverage is 0%, so the description must carry the parameter burden. It does clarify the `casa` parameter indirectly by stating the id originates from buscar_casas, but the `idioma` enum (es/en) is never mentioned, leaving the agent to guess that it controls the language of the returned content.

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 names the resource (a single house) and enumerates exactly what the 'ficha completa' contains: description, amenities present and absent, capacity, price, verification, and already-occupied nights. That enumeration makes it clearly a detail/retrieval tool, distinguishable from the search sibling buscar_casas, though the phrasing is a noun phrase rather than an explicit verb.

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?

It supplies the prerequisite chain for use: 'El id sale de buscar_casas' tells the agent to run the search tool first and feed its result here. There are no explicit exclusions or when-not-to-use notes, which is the only thing separating it from a 5.

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