Skip to main content
Glama

Dunn Estates Aspen: The Galena Penthouse

Amenities

get_amenities
Read-onlyIdempotent

Amenities by room and building (king bed, wood-burning fireplace, full kitchen, Sonos, pool and hot tub, ski storage), what is provided, and what is not available (no elevator, no central A/C, no daily maid service).

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_amenities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
groupsYes
providedNo
notAvailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile needs no restating. The description's genuine addition is signalling that the answer set explicitly includes negatives (unavailable features), which shapes how the agent should read results. It says nothing about scope granularity (per-unit vs per-property) or whether amenities vary between units, which would matter for a lookup tool with no filter parameters.

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?

One front-loaded sentence with the resource and scope first, then illustrative detail; nothing is redundant. The long parenthetical lists are dense but each item adds domain vocabulary an agent can match against a user question.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, a full annotation set, and a declared output schema carrying the return structure, the description only needs to convey what domain of facts lives here — which it does, including the surprising negative facts. Nothing required to invoke it correctly is missing.

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; baseline 4 applies. The parenthetical examples help the agent recognize the domain vocabulary but do not map to any input.

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 a concrete resource (amenities) and scopes it to room- and building-level, with representative examples (king bed, fireplace, Sonos, pool) and explicit negatives (no elevator, no central A/C, no daily maid). An agent can tell this is the amenity-facts lookup rather than a policy or overview tool. It stops short of a differentiating clause naming the nearest siblings (get_property_overview, get_policies).

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?

There is no when-to-use or when-not-to-use guidance and no reference to any of the eight sibling tools. The listed exclusions are about the property (no elevator), not about when to prefer this tool over get_property_overview or get_policies, so routing must be inferred from the name alone.

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