Skip to main content
Glama
Sign In

Usda Soil

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Usda Soil Mapunit At Point

usda_soil_mapunit_at_point
Read-onlyIdempotent

The USDA-NRCS SSURGO soil map unit at one latitude/longitude in the United States — map unit key (mukey), symbol, the official map unit name ("Terril-Urban land complex, 2 to 5 percent slopes"), its acreage, and the soil survey area it belongs to. AUTHORITATIVE for "what soil is on this parcel" in the US: field-surveyed, not modelled. Keyless. Pass the mukey to usda_soil_components for the soil series and their properties.

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

Input Schema

NameRequiredDescriptionDefault
latYesLatitude in decimal degrees, WGS84 (e.g. 41.6).
lonYesLongitude in decimal degrees, WGS84, negative in the US (e.g. -93.6).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safe read-only, idempotent, open-world profile, and the description adds useful context beyond them: 'Keyless', field-surveyed/not modelled authority, and the specific output fields. It still does not cover error behavior or non-soil/water edge cases, so it is not fully exhaustive.

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

Conciseness4/5

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

The description is front-loaded and dense, with purpose, outputs, authority, and routing packed into a short paragraph. The parenthetical example map-unit name is illustrative but slightly over-specific, keeping it from being maximally concise.

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?

For a two-parameter point lookup with no output schema, the description supplies the returned fields, the data source authority, the keyless access model, and the downstream routing tool. No output schema is needed, and the remaining behavioral details are covered by annotations.

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%, and the schema already documents WGS84 decimal degrees, examples, and US-negative longitude. The description adds only the US scope and the phrase 'one latitude/longitude', so the schema does the heavy lifting and this is a baseline 3.

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-like operation (return the USDA-NRCS SSURGO soil map unit) for a precise resource (one lat/lon point in the US), and lists the returned identifiers/attributes. It also distinguishes itself from siblings by explicitly naming usda_soil_components as the next step for soil series data.

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?

Clearly frames the tool as authoritative for 'what soil is on this parcel' in the US and indicates the downstream call to usda_soil_components. It does not, however, explicitly compare against the sibling usda_soil_query or state when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Usda Soil toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources