Skip to main content
Glama

get_property_info

Read-onlyIdempotent

Get property details for a tourism operator.

Returns name, location, description, services summary, and cancellation policy.
Use this to learn about an operator before calling get_services.

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": {
      "operator_id": "<operator_id>"
    },
    "name": "get_property_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
operator_idYesUnique operator slug, e.g. 'fosshotel-reykjavik' or 'arctic-adventures'. Obtain from search_operators. Do not guess — always look up first.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds only the list of returned fields, which is largely duplicated by the output schema, and says nothing about error behavior for unknown operator slugs or lookup cost.

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?

Three short sentences, purpose front-loaded, no filler. The middle sentence enumerating return fields is somewhat redundant given the tool has an output schema, which keeps it from a 5.

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 single-parameter read tool with full annotation coverage and an output schema, the description supplies purpose, prerequisite (operator lookup) and next step. Only the redundant return-field list and absent failure-mode notes leave minor room.

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 operator_id field already explains the slug format, the example values, and the "obtain from search_operators, do not guess" constraint. The description adds no parameter-level meaning beyond that, 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 ("Get property details for a tourism operator") and immediately scopes the result set (name, location, description, services summary, cancellation policy). It also names the sibling it feeds into (get_services), so an agent can place it without opening any schema.

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?

"Use this to learn about an operator before calling get_services" gives a clear sequencing rule and implies the alternative path. There are no explicit exclusions (e.g. when to prefer search_operators or get_about_soley instead), which keeps it short of 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