Skip to main content
Glama

Free camping near a town

free_camping_near_town
Read-onlyIdempotent

USE THIS for "free camping near ", "dispersed camping near" or "boondocking near" a US town (national forest and BLM records we hold; if we hold none it says so). Up to 5 free camps within 25 straight-line miles, nearest first, each with cost evidence, water, nearest toilet, the season reading for today, its record URL, and what is unrecorded. Also gives the site's page for that town when one exists.

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": {
      "town": "<town>"
    },
    "name": "free_camping_near_town"
  }
}

Input Schema

NameRequiredDescriptionDefault
townYesTown name, like "Bozeman" or "Bozeman, MT".
limitNo
stateNoTwo-letter state, if the name is shared.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, and the description still adds real behavior: max 5 results, 25 straight-line miles, nearest-first ordering, per-item cost evidence, water, toilet, season-for-today, record URL, and an explicit unrecorded-data caveat. That is substantive disclosure beyond the structured fields.

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, trigger phrasings front-loaded, and the return-shape sentence justified by the absence of an output schema. No redundant restatement of the name or 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?

With no output schema, describing the returned fields, distance cap, ordering, and coverage limit is exactly what an agent needs. Minor gap: the 'site's page for that town' return element is left unexplained and nothing is said about failure/empty behavior beyond the 'says so' note.

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 coverage is 67%, with town and state documented but limit only carrying a bare default/max/min. The description compensates by stating 'Up to 5 free camps' (explaining the cap) and the distance/ordering semantics, though it never mentions the state parameter or the limit's default of 3.

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?

The description names the exact resource and scope: free/dispersed/boondocking camping near a US town, drawn from national forest and BLM records. It is specific enough to distinguish from a generic camps_near, though it never names a sibling to contrast with.

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?

Opens with an explicit 'USE THIS for' trigger list quoting the user phrasings ('free camping near <town>', 'dispersed camping near', 'boondocking near'), which is strong when-to-use signal. It sets a coverage boundary ('if we hold none it says so') but gives no when-not-to-use or pointer to alternatives such as paid campground lookups.

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