Skip to main content
Glama

Get Soil Properties by Location

soil.survey.properties
Read-onlyIdempotent

Retrieve USDA SSURGO soil properties for any US location by latitude and longitude. Get dominant soil components with depth-stratified horizons including drainage class, pH, organic matter, and texture percentages.

Instructions

Get USDA SSURGO soil properties for a US location by lat/lon (WGS84). Returns dominant component(s) with depth-stratified horizons including drainage class, taxonomic class, pH, organic matter %, and sand/silt/clay percentages per horizon. Coverage: US continental + Alaska + Hawaii + territories; international/water/unsurveyed points return empty components array. Authoritative source: NRCS Soil Data Access (no auth, unlimited free, US Gov open data)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude in WGS84 decimal degrees (e.g. 42.0 for central Iowa farmland, 38.89 for Washington DC). Coverage: US continental + Alaska + Hawaii + territories.
lonYesLongitude in WGS84 decimal degrees (e.g. -93.5 for central Iowa, -77.03 for Washington DC). Note: longitude FIRST in coordinate pairs only matters for SQL — this field is independent.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
Behavior5/5

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

Annotations indicate read-only, idempotent, open-world behavior. The description adds behavioral context beyond annotations: it explains that invalid/uncovered locations return empty components array, and clarifies the authoritative source (NRCS) with no auth and unlimited free usage. No contradictions with annotations.

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?

The description is two sentences with zero waste. It front-loads the core purpose and immediately follows with the return data details, coverage, and authoritative source. Every sentence adds value.

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?

Given the output schema exists (implied by context signals), the description is sufficiently complete. It covers the tool's purpose, input requirements, output structure (dominant components with horizons), geographic scope, edge-case behavior, and source reliability. No additional information seems necessary for an AI agent to use this tool 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?

The input schema already provides full descriptions for both parameters (lat and lon) with coverage notes. The description does not add any parameter-specific semantics beyond what the schema offers, so the baseline of 3 is appropriate given 100% schema coverage.

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?

The description clearly states that the tool gets USDA SSURGO soil properties for a US location by lat/lon, and lists the specific properties returned (drainage class, taxonomic class, pH, organic matter %, sand/silt/clay). It also specifies geographic coverage and edge-case behavior, making it highly distinct from any sibling tools.

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?

The description implicitly guides usage by specifying US-only coverage via lat/lon and what happens for non-US locations. It does not explicitly name alternatives or provide when-not-to-use guidance, but the context is clear given the tool's specialized data type (soil) and the sibling list shows no similar tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/whiteknightonhorse/APIbase'

If you have feedback or need assistance with the MCP directory API, please join our Discord server