Skip to main content
Glama

Blm Claims Near

blm_claims_near
Read-onlyIdempotent

US federal mining claims (BLM MLRS) within a radius of a latitude/longitude, e.g. claims staked around a lithium, gold or uranium deposit in Nevada, Arizona, Utah, Wyoming. Returns the total count in the radius plus a page of claims (each page sorted by distance): BLM case serial number, claim name, type (lode / placer / mill site / tunnel site), status (Active, Filed, Closed...), recorded acres, distance, and an MLRS case-record link. Geometry is the recorded PLSS land description, not the staked boundary.

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": 5,
      "latitude": 41.71,
      "longitude": -118.06,
      "radius_km": 10
    },
    "name": "blm_claims_near"
  }
}

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".
latitudeYesLatitude (WGS84), e.g. 41.71
longitudeYesLongitude (WGS84), e.g. -118.06
radius_kmNoSearch radius in km, 0.1-50 (default 5)
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. Changed3 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 / radius_km / description
      Previous value: -"Search radius in km, 0.1–50 (default 5)"New value: +"Search radius in km, 0.1-50 (default 5)"
    • 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

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, idempotent, non-destructive, so the bar is lower. The description still adds real value beyond them: it discloses the return shape (total count plus a distance-sorted page), the fields returned, and an important data-quality caveat that geometry is the recorded PLSS land description rather than the staked boundary.

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?

Three tight sentences, front-loaded with the resource and spatial scope, then results, then the geometry caveat. Nothing is redundant and the caveat is placed where an agent will read it before acting.

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 burden of explaining return values, and it does — count, paged claims, per-claim fields, sort order. Combined with full schema coverage and read-only annotations, an agent has everything needed to call it correctly.

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, enum, default and range is already documented in the schema. The description only restates values (claim types, statuses, acres, distance) without adding interpretation, so the 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?

States a specific verb+resource+scope: 'US federal mining claims (BLM MLRS) within a radius of a latitude/longitude,' with concrete examples (lithium/gold/uranium in NV, AZ, UT, WY). It implicitly differentiates from case-level or bbox siblings by naming the radius search, though it never names an alternative tool.

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?

Usage is only implied by the example scenarios ('claims staked around a lithium, gold or uranium deposit'). There is no explicit when-to-use vs when-not guidance and no routing between this radius search and the bbox or case siblings, which is the most likely source of misselection.

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.