Skip to main content
Glama

FillPoint archived station proximity

find_rv_stations
Read-only

Use when you need nearby RV stations from the dated FillPoint snapshot; see Data APIs. Nearest RV dump/water stations from FillPoint RV's dated September 17, 2026 ODbL snapshot. $0.01 for bounded straight-line proximity calculation, not live access, potable-water assurance or road routing. Snapshot age and unknown current conditions are explicit. Full underlying projection is free under ODbL. Price: 0.01 USDC. Minimal input example: {"latitude":42.07,"longitude":-88.36,"radius_km":50,"limit":10,"service":"dump"}. Illustrative output excerpt: {"results":[],"distance_method":"great_circle_not_road_distance"}. Illustrative output excerpt, not a live result, signature, approval or guarantee. Freshness/data/availability checks still apply. How to pay (MCP): First use the existing shared allowance of 3 eligible calls per IP per UTC day, without payment metadata. This is shared with eligible HTTP trials, not a new allowance. Use an x402-capable MCP client. A generic MCP connector without payment support cannot complete a paid continuation. On payment required, STOP. Inspect the exact accepts amount, asset, network and payTo; obtain explicit wallet/budget approval before continuing. Only after approval, let the configured x402 MCP client attach its signed payload in _meta["x402/payment"] and retry the same tools/call arguments. Never send a separate USDC transfer or paste keys into tool arguments. Never silently fall back from free access to payment. If a signed attempt has an unknown outcome, inspect that authorization/transaction; do not create another automatically.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "find_rv_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional. Maximum result count integer, 1–50. Example: 10. Defaults to 10.
serviceNoOptional. Archived service filter enum string: dump, water or either. Example: water. Defaults to either.either
latitudeYesRequired. Latitude number in decimal degrees, -90 to 90. Example: 34.05.
longitudeYesRequired. Longitude number in decimal degrees, -180 to 180. Example: -118.25.
radius_kmNoOptional. Search radius number in kilometres, 0.1–500. Example: 50. Defaults to 50 km.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / latitude / description
      Added value: +"Required. Latitude number in decimal degrees, -90 to 90. Example: 34.05."
    • addedInput schema / properties / limit / description
      Added value: +"Optional. Maximum result count integer, 1–50. Example: 10. Defaults to 10."
    • addedInput schema / properties / longitude / description
      Added value: +"Required. Longitude number in decimal degrees, -180 to 180. Example: -118.25."
    • addedInput schema / properties / radius_km / description
      Added value: +"Optional. Search radius number in kilometres, 0.1–500. Example: 50. Defaults to 50 km."
    • addedInput schema / properties / service / description
      Added value: +"Optional. Archived service filter enum string: dump, water or either. Example: water. Defaults to either."
  2. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description adds substantial non-redundant behavior: a $0.01 USDC price, a shared 3-calls-per-IP-per-UTC-day free allowance, the fact that results come from a dated snapshot with unknown current conditions, and that distances are great-circle rather than road distance. It also documents the x402 payment continuation protocol, the requirement for explicit wallet approval, and the rule not to auto-retry on unknown outcomes. Nothing here contradicts readOnlyHint (no writes are claimed) or openWorldHint=false (explicitly not live).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose takes one sentence, but the body is dominated by payment-flow instructions, repeated disclaimers ("Illustrative output excerpt, not a live result, signature, approval or guarantee. Freshness/data/availability checks still apply"), and near-duplicate caution language. Several sentences restate the same caveat about the snapshot not being live. The signal-to-noise ratio is poor for an agent trying to decide whether to call the tool.

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, the description supplies an illustrative output excerpt including distance_method, plus pricing, free-tier terms, and snapshot freshness caveats — enough for an agent to call the tool and interpret results. The main gap is the vague "see Data APIs" reference and the absence of guidance on what an empty results array implies. For a paid, snapshot-based lookup it is largely 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 every parameter (latitude, longitude, radius_km, limit, service) is already documented with ranges, defaults, and examples. The description's only added semantic nuance is that proximity is "bounded straight-line" / great-circle rather than road distance, which clarifies how radius_km should be interpreted. That is a marginal increment over a fully documented schema, so baseline 3 applies.

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 a concrete verb and resource: "Nearest RV dump/water stations from FillPoint RV's dated September 17, 2026 ODbL snapshot," and the lead sentence states the use case directly. It also delineates scope by negation ("not live access, potable-water assurance or road routing"), so an agent knows this is a snapshot proximity lookup. It stops short of a 5 because the actual purpose statement is buried among pricing and payment boilerplate rather than being the dominant line.

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?

"Use when you need nearby RV stations from the dated FillPoint snapshot" gives an explicit trigger, and the exclusions (not live access, not road routing, not potable-water assurance) tell the agent when this tool is the wrong choice. The alternative pointer "see Data APIs" is vague and off-tool, so there is no concrete named alternative. Overall it is clear usage context without a strong routing statement.

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.