Skip to main content
Glama

Price a short stay for dates

get_stay_pricing
Read-onlyIdempotent

Check whether a short-stay holiday let (stay_id from search_stays) is available for check_in / check_out (YYYY-MM-DD) and price it: nights, nightly rate, subtotal, cleaning fee and total, plus a bookUrl with the dates filled in. Booking takes payment and an account, so it finishes at bookUrl — never collect card details.

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": {
      "stay_id": "<stay_id>",
      "check_in": "<check_in>",
      "check_out": "<check_out>"
    },
    "name": "get_stay_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
guestsNo
stay_idYes
check_inYesYYYY-MM-DD
check_outYesYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description is consistent with a non-mutating price check. It adds real value by describing the returned breakdown and by disclosing that the tool's output is a hand-off point (bookUrl with dates filled in) rather than a completed booking, which prevents an agent from collecting payment details. It does not say whether quotes expire or are guaranteed, which would be the last piece of behavioral context.

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?

Two sentences: a dense but front-loaded capability statement, then a short safety constraint. The long output enumeration earns its place since there is no output schema, and there is no filler wording. Slightly heavy for a single sentence, but nothing to cut.

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 read-only pricing tool with no output schema, the description covers the operation, the input provenance, the return breakdown and the hand-off boundary. The only shortfall is the unexplained guests parameter, which matters for a holiday let where occupancy affects price.

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 50%: check_in and check_out already carry the YYYY-MM-DD format in the schema, so the description mostly restates it. It does add provenance for stay_id (come from search_stays), which the schema lacks, but the guests parameter is undocumented in both the schema and the description, leaving one of four parameters with no semantics anywhere.

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 pair (check availability + price) on a specific resource (short-stay holiday let), and enumerates the exact outputs (nights, nightly rate, subtotal, cleaning fee, total, bookUrl). It also anchors stay_id to its source (search_stays), so an agent can distinguish this from the search siblings without opening a 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?

Gives a clear workflow context: stay_id must come from search_stays, and pricing is the last step before a bookUrl hand-off. It also draws an explicit boundary (never collect card details; booking requires an account and payment) which tells the agent when to stop using this tool. The only gap is that it does not name which tool or flow handles the actual booking beyond the returned URL.

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