Camping Australia

Search things to do

bk_search_content

Read-onlyIdempotent

Search curated tourism content (attractions, things to do, local experiences, events) from our booking partner. Use this for 'what's on / things to do near X' style questions — this is content we do NOT have in our own directory. NOT for campsite/accommodation booking (use the other bk_ tools for that).

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": {
      "query": "<query>"
    },
    "name": "bk_search_content"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max results (default 6)
`query`	Yes	What to search for (e.g. 'things to do near Jervis Bay')

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world search. The description adds useful behavioral context by noting the content comes from a booking partner and is not in the service's own directory, though it does not discuss result format or pagination.

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?

The description is concise and front-loaded: it first states what is searched, then gives the use case, then the exclusion. Every sentence contributes useful selection information.

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 two-parameter search tool with complete annotations and full schema coverage, the description provides enough context to select and invoke it correctly. A minor gap is that it does not describe result shape or volume, but no output schema exists and the core selection guidance is complete.

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

Parameters3/5

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

Schema description coverage is 100%, so both the query and limit parameters are already documented in the schema. The description does not add syntax or filtering details beyond what the schema provides, making the baseline score appropriate.

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 states a specific verb and resource: search curated tourism content including attractions, things to do, local experiences, and events from a booking partner. It also distinguishes the scope from the sibling bk_ tools by explicitly excluding campsite/accommodation booking.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance for 'what's on / things to do near X' questions and states a clear exclusion: not for campsite/accommodation booking, where the other bk_ tools should be used. This routes the agent effectively among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Camping Australia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?