Skip to main content
Glama

Casa Rosanna – Porto Ottiolu, Sardinia

house_info

Key facts about Casa Rosanna: location, rooms, amenities, check-in times, pets, contacts. / Dati principali della casa.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "house_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and says nothing about whether the content is a fixed snapshot or dynamically fetched, whether it requires network calls, or that the call is free of side effects and safe to repeat. The only behavioral hint is the bilingual text, which implies a bilingual dataset but is not stated as such.

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?

The content is front-loaded into a single compact sentence and fits comfortably in a selection context. The second, Italian sentence repeats the same meaning without adding information for an agent, which is a minor waste rather than a defect.

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 zero-parameter, read-only information tool with no output schema, the description lists the topics covered, which is the main thing an agent needs to judge relevance. What is missing is only the framing (static snapshot, no side effects) rather than anything required to invoke it correctly.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The enumerated content list does at least tell the agent what the no-argument response covers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the content of the tool (location, rooms, amenities, check-in times, pets, contacts) for a named property, so an agent can infer it returns static house facts. However, there is no verb ("retrieve"/"get") and no statement of what is returned versus what a caller might expect, leaving the purpose implied rather than stated. It is distinguishable from siblings (beach_today, check_availability, list_weeks) only by topic, not by any explicit differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides no when-to-use guidance, no prerequisites, and no mention of the sibling tools or when one of them would be the better choice. The agent must infer that this is the static-information tool used when the question is about the house itself rather than availability.

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