Skip to main content
Glama
Sign In

Usda Soil

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Usda Soil Components

usda_soil_components
Read-onlyIdempotent

The soil components inside one USDA SSURGO map unit — each named soil series with its percentage of the unit, official taxonomic class, drainage class, slope range, hydrologic soil group, land capability class and runoff potential. Answers "what soil series is this and how does it drain/behave". Keyless. Get the mukey from usda_soil_mapunit_at_point.

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": {
      "mukey": "412898",
      "include_horizons": true
    },
    "name": "usda_soil_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
mukeyYesSSURGO map unit key, e.g. "412898". From usda_soil_mapunit_at_point.
include_horizonsNoAlso return the soil horizons (depth layers) for each component with sand/silt/clay percentages, organic matter, pH and available water capacity. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added "Keyless" note and the enumeration of returned fields are genuinely extra context. It does not discuss pagination or limits, but for a small keyed lookup this is adequate.

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?

Front-loads the resource and its purpose, then tacks on the prerequisite source in a short sentence. The field list is long but each item conveys real return content rather than padding.

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 no output schema, the description carries the return-shape burden and does so by listing the component attributes. Prerequisite (mukey source) and keyless access are covered; only the include_horizons output is left to the schema.

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 coverage is 100% and both parameters are documented in the schema (including include_horizons and its effect). The description adds no parameter-level detail, so it sits at the baseline where the schema does the work.

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/resource — the soil components within one USDA SSURGO map unit — and enumerates the exact returned attributes (series name, percentage, taxonomy, drainage, slope, hydrologic group, land capability, runoff). An agent can distinguish it from usda_soil_mapunit_at_point (which yields the mukey) and usda_soil_query without opening a schema.

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?

Explains when it applies via the quoted question "what soil series is this and how does it drain/behave" and names the upstream sibling as the mukey source. No explicit when-not or exclusion against usda_soil_query, so it stops short of full conditional routing.

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