Skip to main content
Glama

Dunn Estates Aspen: The Galena Penthouse

Stay policies

get_policies
Read-onlyIdempotent

Check-in and check-out times, minimum age, maximum guests, pets, smoking, quiet hours, parking, housekeeping, minimum-stay rules, taxes and how quotes and cancellations work, as stated in the official property listing.

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": "get_policies"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
petsYes
taxesNo
quotesNo
sourceNo
checkInYes
parkingNo
smokingYes
checkOutYes
maxGuestsNo
minimumAgeNo
quietHoursNo
minimumStayNo
selfCheckInNo
cancellationNo
housekeepingNo
lastVerifiedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 safety behavior is fully covered by structured data. The description adds that content is 'as stated in the official property listing', signalling authoritative, verbatim listing text rather than computed values, but it does not say what happens when a policy is unstated or how current the text is.

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?

A single dense sentence with no filler, and every listed topic earns its place by telling the agent what is in scope. It is slightly list-heavy and does not front-load a purpose statement, but nothing is redundant.

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 shapes and field names need not be explained here, and with no input parameters the description's only job is to frame scope and source, which it does. The one remaining gap is guidance on overlap with siblings and on handling missing policies, which keeps it below 5.

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 the baseline is 4 and there is no parameter meaning the description could add. The topic enumeration is genuinely useful context, but it describes the payload rather than any argument semantics.

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 enumerates the exact policy topics the tool returns (check-in/out times, minimum age, max guests, pets, smoking, quiet hours, parking, minimum-stay, taxes, quotes, cancellations) and pins the source to the 'official property listing', which clearly separates it from siblings like get_amenities or get_location_and_nearby. It never uses an explicit verb such as 'returns' or 'retrieves', relying on the name plus topic list to convey the action, so it falls just short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the right tool when a user asks about stay rules. There is no explicit when-to-use statement, no mention of when NOT to use it, and no routing to alternatives such as get_amenities for pet-related amenities or get_quote for pricing details, even though those overlap with topics listed here.

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