Skip to main content
Glama

Book a CityScape stay

cityscape_create_booking

Create a CityScape booking on a user's behalf. ai-assisted returns a checkout link for the human to pay; corporate-ai charges a pre-authorized on-file card (10% discount) and requires a paymentMethodId.

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": {
      "listingId": "<listingId>",
      "from": "<from>",
      "to": "<to>",
      "guests": "<guests>",
      "bookingKind": "<bookingKind>"
    },
    "name": "cityscape_create_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesCheck-out date (YYYY-MM-DD).
fromYesCheck-in date (YYYY-MM-DD).
guestNo
apiKeyNoAPI key for the write path. Required unless the server was started with AGENT_API_KEY.
guestsYesNumber of guests.
listingIdYesListing slug.
bookingKindYesai-assisted = a human completes payment; corporate-ai = the AI completes payment (10% discount).
paymentMethodIdNoRequired for corporate-ai: a pre-authorized on-file Stripe PaymentMethod (pm_…).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key behavioral split: one path defers payment to a human via a returned checkout link, the other charges a pre-authorized card with a 10% discount. It does not cover idempotency, whether charges are reversible/refundable, or failure modes, which are meaningful gaps for a payment-taking mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both front-loaded with the core action and the mode distinction, with zero filler. Every clause earns its place by distinguishing behavior between the two enum branches.

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

Completeness3/5

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

There is no output schema, so the description should ideally cover return values; it does explain the ai-assisted checkout link but says nothing about what corporate-ai returns (confirmation, booking id, charge result). For an 8-parameter payment mutation with no annotations, more completeness would be expected.

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 description coverage is 88%, so the schema already documents bookingKind, paymentMethodId, dates, guests, listingId, and apiKey. The description adds only the conditional linkage that paymentMethodId is required when bookingKind is corporate-ai, which is marginally beyond the schema's own per-field text. Baseline 3 is appropriate.

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?

States a specific verb+resource ("Create a CityScape booking") and the scope ("on a user's behalf"), which clearly separates it from the read-only siblings check_availability and get_quote. It stops short of naming those siblings or contrasting with them explicitly, so it is clear but not differentiated in-text.

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?

The description explains the two operating modes and the condition that selects each: ai-assisted produces a checkout link for a human to pay, while corporate-ai charges an on-file card and requires a paymentMethodId. That is real when-to-use guidance for the branching behavior, though it gives no sequencing relative to get_quote or availability checks.

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