Experience Bamfield

Cottage prices for exact dates

price_cottages

Read-onlyIdempotent

Every cottage's price for a stay, whether it is free, and whether it sleeps the party. The figures are before the cleaning fee and taxes: quote_trip gives the all-in total.

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": {
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "price_cottages"
  }
}

Input Schema

Name	Required	Description
`guests`	No	How many people.
`endDate`	Yes	Check-out: the morning the guests leave.
`startDate`	Yes	Check-in.

Output Schema

Name	Required	Description	Default
`note`	No
`guests`	No
`nights`	No
`cottages`	Yes
`ratesKnownThrough`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: results are per-cottage, flag free stays and party fit, and explicitly exclude the cleaning fee and taxes. This is meaningful cost-semantics disclosure that annotations cannot carry.

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 sentences, no filler. The output scope is front-loaded and the cost caveat/routing note is compressed into a single clause after the colon.

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?

An output schema exists, so return values need not be described. The description covers the two things an agent cannot get from structured fields: what the figures exclude and which sibling to use for a total. Nothing needed to call it correctly is missing.

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 description coverage is 100%, so the baseline is 3. The description earns above baseline by explaining that the guest count is used to evaluate 'whether it sleeps the party' — a semantic purpose the schema's 'How many people.' does not convey.

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 resource and scope: 'Every cottage's price for a stay', plus two derived outputs (whether it is free, whether it sleeps the party). It also distinguishes itself from the sibling quote_trip by reserving the all-in total for that tool. An agent can tell exactly what this returns without opening a schema.

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?

It names the alternative tool (quote_trip) and the condition that selects it ('the all-in total'), which is solid routing guidance. It stops short of an explicit when-to-use/when-not framing (e.g. comparing cottages vs. committing to a booking), so it is clear context rather than full guidance.

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

All Experience Bamfield 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?