Skip to main content
Glama

Noosa tours and bike hire (By Earth and Ocean, Bike On)

Check rental availability

check_rental_availability
Read-only

Live availability and price for Bike On rental bikes over a date range, by size item_id, plus the delivery charge if a suburb is given. Each size suits a range of rider heights.

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": {
      "bikes": "<bikes>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "check_rental_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
bikesYes
end_dateYesLast day of hire, YYYY-MM-DD (same as start_date for one day)
start_dateYesFirst day of hire, YYYY-MM-DD
delivery_suburbNoOptional: suburb to deliver to and collect from. Leave out to collect from the shop.

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?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds context the annotations do not: results are live, they include pricing, and delivery charge appears conditionally on the suburb being supplied — useful for interpreting output on a tool with no output schema. It stops short of stating pricing units or failure behavior for unavailable sizes.

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 tight sentences, front-loaded with the resource and scope, with no redundant restatement of the title or annotations. Every clause carries information: what is returned, how bikes are keyed, and the delivery condition.

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?

With no output schema, the description carries the burden of describing returns and does so (availability, price, delivery charge), which is the key gap for a read tool. Minor omissions remain — no statement of what happens when a size is unavailable and no pricing unit — but the agent has enough to invoke it correctly.

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?

The schema covers 75% of parameters, and the description adds meaning on top: 'by size item_id' plus 'Each size suits a range of rider heights' explains what item_id represents beyond the schema's pointer to list_rentals, and 'plus the delivery charge if a suburb is given' explains the consequence of delivery_suburb. The date-range framing reinforces start_date/end_date semantics already documented in the schema.

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 and resource ('Live availability and price for Bike On rental bikes') and scopes it to a date range and size item_id, so it is clearly distinct from a generic availability check or a booking tool. It does not explicitly name the sibling it differs from (e.g. check_availability for tours), which keeps it from a 5.

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 implied rather than stated: the description conveys that this is the pre-booking lookup for rentals over a date range, and the schema notes item_id comes from list_rentals. There is no explicit when-to-use/when-not guidance or named alternative, so an agent must infer the routing.

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