Skip to main content
Glama

Best nights to book

best_nights
Read-onlyIdempotent

The cheapest checked nights for a Las Vegas Strip hotel in a date range, with what is on those nights. Defaults to the next four months.

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

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 is covered elsewhere. The description contributes useful behavior beyond that: the default date window is the next four months and the response accompanies prices with local events. It does not say what happens when no nights qualify, or how prices are sourced/curated beyond the vague word 'checked'.

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 tight sentence with the resource and the date-range default front-loaded, and no filler. It loses a point only because 'checked nights' is opaque terminology that a reader must decode.

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?

For a three-parameter read-only query with no output schema, the definition covers the core intent and the default window, which is enough to attempt a call. But with zero schema parameter coverage and no output schema, the undocumented limit semantics and date format leave real gaps an agent must guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for from/to/limit, yet it only implies that the two date parameters exist and that they default to a four-month window. Date format is unstated, and 'limit' is never explained at all – an agent cannot tell whether it caps the number of nights returned or something else, despite a maximum of 10.

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 outcome: returns the cheapest nights for a Las Vegas Strip hotel within a date range, and bundles in what is happening on those nights. The resource and the returned value are both identifiable, though the phrase 'checked nights' is unusual jargon and the description never distinguishes this from the sibling hotel_prices tool.

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 explicit when-to-use or when-not-to-use guidance, and no mention of the obviously adjacent hotel_prices sibling. The only contextual hint is the default window of 'the next four months', which tells an agent what happens when it omits arguments but not why it should pick this tool over the alternative.

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