Skip to main content
Glama

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

List rental bikes

list_rentals
Read-only

List Bike On bike rentals in Noosa (e-bike cruisers, fat tyre e-bikes, mountain and e-mountain bikes, road and gravel bikes, kids and family bikes). Each bike shows its sizes with the rider height each size suits. Delivery areas and minimums are included.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 genuine value beyond that by disclosing the payload contents: per-bike sizes mapped to rider heights, plus delivery areas and minimums.

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 front-loaded sentences: the resource first, then what each record contains. The parenthetical category list is long but earns its place by telling the agent what coverage to expect.

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 input parameters and no output schema, the description usefully carries the burden of describing the response shape (sizes, rider heights, delivery areas, minimums). No pagination or result-count guidance is given, but that is a minor omission for an unfiltered catalog tool.

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 tool takes zero parameters, so there is nothing to disambiguate and the baseline is a 4. The description correctly avoids inventing filter arguments that the schema does not support.

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 ('List Bike On bike rentals in Noosa') and enumerates the catalog categories covered, so an agent knows exactly what comes back. It does not explicitly contrast itself with check_rental_availability, so sibling differentiation is left implicit.

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?

Browsing a rental catalog implies this is the discovery step before check_rental_availability or create_booking, and the mention of delivery areas and minimums hints at info gathered before booking. However, there is no explicit when-to-use or when-not-to-use statement and no named 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