Skip to main content
Glama

blm_land_lookup

Read-only

Look up Bureau of Land Management land status for a US coordinate: BLM ownership, jurisdiction, allowed activities (rockhounding, camping), permit requirements, and special designations (ACEC, Wilderness, WSA, NM/NCA).

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "blm_land_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude, -90 to 90.
lonYesLongitude, -180 to 180.
radius_kmNoOptional buffer radius in km (0-50, default 1.0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds useful behavioral context by naming the returned dimensions: ownership, jurisdiction, allowed activities, permit requirements, and special designations. It does not discuss data freshness, provenance, or limitations, which keeps it from a 5.

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?

A single dense sentence with the verb and resource front-loaded, followed by a compact enumeration of returned categories. There is no redundant or filler wording.

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?

For a simple read-only lookup with a fully described input schema and no output schema, the description gives enough scope and output categories for an agent to call it correctly. It could be slightly more complete by mentioning return format or data limitations, but the core information is present.

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 the input schema already documents lat, lon, and radius_km. The description only reinforces that the tool expects a US coordinate; it adds no additional meaning about coordinate precision, radius behavior, or edge cases beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Look up'), resource ('Bureau of Land Management land status'), scope ('for a US coordinate'), and enumerates the returned categories. An agent can immediately tell this is a read-only land-status lookup rather than a generic coordinate or mapping 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?

The description implies usage for US coordinates needing BLM status and lists what the result covers, but it does not explicitly say when to use this tool versus alternatives or when not to use it. The sibling tools are unrelated, so the lack of alternative routing is less harmful, but usage guidance remains implicit.

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.