Skip to main content
Glama

Blm Claims In Bbox

blm_claims_in_bbox
Read-onlyIdempotent

US federal mining claims (BLM MLRS) inside a latitude/longitude bounding box (up to 2° on a side). Returns the total count in the box and a page of claims: BLM case serial number, claim name, lode/placer/mill-site type, status, acres, mapped center and an MLRS case-record link.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 3,
      "max_lat": 37.85,
      "max_lon": -117.45,
      "min_lat": 37.7,
      "min_lon": -117.65
    },
    "name": "blm_claims_in_bbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoClaims to return, 1-500 (default 50)
statusNoWhich claims: "open" (default, every claim not closed: Active, Filed, Under Review, On Appeal...), "active" (disposition exactly Active), "closed", or "all".
max_latYesNorth edge latitude
max_lonYesEast edge longitude
min_latYesSouth edge latitude
min_lonYesWest edge longitude
claim_typeNoOptional claim type filter: lode, placer, mill_site or tunnel_site.
after_object_idNoPaging cursor: pass next_after_object_id from the previous page (default: first page)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Claims to return, 1–500 (default 50)"New value: +"Claims to return, 1-500 (default 50)"
    • changedInput schema / properties / status / description
      Previous value: -"Which claims: \"open\" (default — every claim not closed: Active, Filed, Under Review, On Appeal…), \"active\" (disposition exactly Active), \"closed\", or \"all\"."New value: +"Which claims: \"open\" (default, every claim not closed: Active, Filed, Under Review, On Appeal...), \"active\" (disposition exactly Active), \"closed\", or \"all\"."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds genuinely new behavior: a hard 2° bbox limit, that results are paginated with a total count plus one page, and exactly which fields come back. It stops short of noting ordering or how the count relates to the paged subset.

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 tight sentences: the first establishes scope and the hard constraint, the second enumerates the return shape. No filler and the constraint is front-loaded where an agent will read it.

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?

With no output schema, the description carries the return-value burden and does so by listing the fields and the count-plus-page structure. Combined with 100% schema coverage on 8 parameters, an agent has everything needed to call this correctly.

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 100%, so baseline is 3, and the description contributes real added meaning by imposing the 'up to 2° on a side' constraint on the four coordinate parameters, which the schema does not state. It does not explain the limit/status/claim_type interplay, but the schema already handles those enums well.

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?

Names a specific resource (US federal mining claims via BLM MLRS) and a specific spatial operation (query inside a lat/lon bounding box), plus the exact return payload (count, serial number, name, type, status, acres, center, case link). It stops short of distinguishing itself from siblings like blm_claims_case or blm_claims_near, so an agent must infer that bbox differs from a point-radius or single-case lookup.

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?

The 2°-per-side cap implies when this tool is and isn't appropriate (large regions need tiling), but there is no explicit statement of when to prefer it over blm_claims_near or blm_claims_summary. Usage is inferable from the spatial framing rather than stated.

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.