Skip to main content
Glama

Blm Claims Summary

blm_claims_summary
Read-onlyIdempotent

Counts of US federal mining claims (BLM MLRS) within a radius of a point, broken down by claim type and status, with total recorded acres, how heavily staked is the ground around a deposit or project site, and how much of it is active versus closed.

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

Input Schema

NameRequiredDescriptionDefault
statusNoWhich claims: "open" (default, every claim not closed: Active, Filed, Under Review, On Appeal...), "active" (disposition exactly Active), "closed", or "all".
latitudeYesLatitude (WGS84)
longitudeYesLongitude (WGS84)
radius_kmNoRadius in km, 0.1-50 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / radius_km / description
      Previous value: -"Radius in km, 0.1–50 (default 10)"New value: +"Radius in km, 0.1-50 (default 10)"
    • 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.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real value by disclosing what comes back: counts broken down by claim type and status, total recorded acres, and an active-versus-closed split. It omits data freshness and the fact that radius is capped (that limit lives only in the schema).

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

Conciseness3/5

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

It is a single front-loaded sentence, which is good, but it is a run-on that repeats the same idea twice: "broken down by claim type and status" is restated as "how much of it is active versus closed." Trimming the marketing-flavored clause about staking would make it tighter.

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 four parameters, no output schema, and full schema coverage, the description carries the burden of describing return values and does so adequately. For a read-only aggregation tool this is close to sufficient; only the missing differentiation from the bbox/near siblings keeps it from full marks.

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%, including the enum meanings for status and the 0.1-50 km radius range, so the baseline is 3. The description restates the radius and status concepts without adding format or syntax detail beyond what the schema already provides.

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 ("Counts"), a specific resource ("US federal mining claims (BLM MLRS)"), and a scope ("within a radius of a point"), plus the aggregation dimensions (claim type, status, acres). It does not distinguish itself from close siblings such as blm_claims_in_bbox or blm_claims_near, so an agent must infer that this is the aggregate/count variant rather than a record-returning one.

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 through the phrase "how heavily staked is the ground around a deposit or project site," which hints at a screening/due-diligence use case. There is no explicit when-to-use, no when-not-to-use, and no pointer to the bbox or near siblings, leaving the agent to guess between four similar claims tools.

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.