Skip to main content
Glama

Look up a rental

product_info
Read-only

Look up a Sky High rental product by name. Returns the page URL, units in stock, how many times families have booked it, and price. ALWAYS pass event_date (and zip when you know it) - with a date this returns the EXACT price for that date and whether it is available, which you should quote directly. Prices returned here are LIVE - prefer them over any knowledge-file price, and never send the customer to the product page to find a price this tool can give you.

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": {
      "product_name": "<product_name>"
    },
    "name": "product_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNo5-digit delivery zip, when known. Selects the right metro's pricing.
event_dateNoEvent date YYYY-MM-DD. Always pass it when the customer has said their date - it returns the exact price for that day.
product_nameYesProduct name or close description, e.g. 'Niagara water slide'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds genuinely non-structured context: the prices are LIVE and date-dependent, an event_date yields the exact price and availability for that day, and the result should be quoted verbatim rather than deferred to. It stops short of describing behavior on a miss (no product found) or multiple matches for a fuzzy name.

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 with purpose, then return fields, then the imperative parameter rule, then the price-authority caveat — a sensible order with no filler. Slightly redundant, as price is mentioned in the returns list and again twice in the final sentences, which costs it a point.

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?

There is no output schema, so the description carries the full burden of describing returns, and it does: URL, stock, booking count, price, plus availability when a date is supplied. Combined with 100% schema coverage and read-only annotations, an agent has everything needed to call this correctly and interpret the result.

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%, so baseline is 3; the description earns the bump by explaining the consequence of each parameter rather than just its type — event_date changes the price from generic to exact, and zip selects the metro's pricing. It also elevates event_date to a 'always pass it' rule, which is behavioral guidance the schema only weakly implies.

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 and resource ('Look up a Sky High rental product by name') and immediately enumerates what comes back (page URL, units in stock, booking count, price). An agent can distinguish this from add_to_cart, build_quote, delivery_fee, and prepare_checkout without opening any schema, since none of those is a product lookup.

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 explicit operational guidance: always pass event_date, add zip when known, quote the returned price directly, and prefer it over knowledge-file prices or sending the customer to the product page. It names the alternatives it supersedes (knowledge file, product page) but never addresses the sibling tools (add_to_cart, build_quote) or when to move from lookup to those, so the routing picture is incomplete.

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