Skip to main content
Glama

Get unit details

get_unit_details
Read-onlyIdempotent

Get full description, amenities, access notes, and policies for a unit.

Args:
    unit: One of "muckle-meadow-pod", "cosie-coorie-pod", "bb".
          For "bb", returns the 4 rooms plus shared amenities.

Returns:
    {unit, details: {name, type, size_sqm, amenities, rooms?, ...},
     policies, location}.

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": {
      "unit": "<unit>"
    },
    "name": "get_unit_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYesWhich WEE WiLDS unit: "muckle-meadow-pod" (Muckle Meadow Glamping Pod), "cosie-coorie-pod" (Cosy Coorie Pod) or "bb" (the B&B, all 4 rooms).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / unit / description
      Added value: +"Which WEE WiLDS unit: \"muckle-meadow-pod\" (Muckle Meadow Glamping Pod), \"cosie-coorie-pod\" (Cosy Coorie Pod) or \"bb\" (the B&B, all 4 rooms)."
    • addedInput schema / properties / unit / enum
      Added value: +[
      +  "muckle-meadow-pod",
      +  "cosie-coorie-pod",
      +  "bb"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/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 the safety profile is covered. The description adds real behavioral value beyond that by disclosing the special 'bb' behavior (returns the 4 rooms plus shared amenities) and sketching the return payload; it does not, however, mention error behavior for an invalid unit.

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?

Front-loaded purpose sentence followed by Args and Returns blocks is easy to scan. The Args block partially restates the enum already present in the schema, which is mild redundancy, but the Returns sketch earns its space since no output schema exists.

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 a fully described schema, the definition is largely complete, and the informal output shape compensates for the missing output schema. The trailing '...' and absent malformed-input behavior leave only small gaps.

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?

Schema coverage is 100% and the enum values already carry descriptions, so the schema does most of the work. The description goes one step further by explaining the consequence of a specific enum choice ('bb' yields 4 rooms plus shared amenities), which is meaning the schema does not convey.

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 opens with a specific verb and resource plus an enumerated payload: 'Get full description, amenities, access notes, and policies for a unit.' That field list implicitly separates it from get_availability and get_pricing, but no sibling is named, so an agent must infer the routing itself.

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 tell this is the detail-lookup call, and the 'bb' note hints at when the result set is broader. There is no explicit when-to-use, when-not-to-use, or pointer to get_availability/get_pricing as alternatives.

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