Skip to main content
Glama

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

List tours

list_tours
Read-only

List By Earth and Ocean tours in Noosa (kayak tours on the Noosa Everglades with stingrays, guided and self guided e-bike and mountain bike tours, fat bike beach rides). Returns each tour key, description, page and its session times.

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_tours"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 the safety profile is covered. The description adds genuine value beyond that by naming the returned fields — tour key, description, page, and session times — which tells the agent what payload to expect and that session schedules are embedded. It does not discuss result volume or ordering, which is the only remaining gap for a zero-param listing.

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 sentences, front-loaded with the resource and scope, then the return contract. The parenthetical tour-type list is slightly long but earns its place by defining catalog breadth. No filler or redundant restatement of the title.

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?

For a simple zero-parameter read tool with no output schema, the description supplies what an agent needs: scope, included tour categories, and the fields returned. The absence of pagination or ordering notes is minor given the closed-world, non-destructive annotations.

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 has zero parameters and the schema is empty, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly does not waste words restating a non-existent input contract.

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?

The description opens with a specific verb+resource ("List By Earth and Ocean tours in Noosa") and immediately scopes what kinds of tours are included (kayak, e-bike, mountain bike, fat bike). It also enumerates what each record contains, so an agent can distinguish this catalog tool from siblings like list_rentals or check_availability without opening any schema.

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 only implied: the tool takes no parameters, so the natural reading is "call this to enumerate the tour catalog." There is no explicit when-to-use or when-not-to-use statement, and no alternative is named for cases like checking whether a specific tour has open slots (a job check_availability presumably handles). Adequate but leaves routing to inference.

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