Skip to main content
Glama

farmland-soil-report

Farmland Soil, Water & Drought Report — Before buying, leasing or planting a US parcel, reads the USDA NRCS soil survey at a point (lat/lon or US address): map unit, prime farmland class, land capability class and subclass, drainage, hydric rating, flooding and ponding frequency, water table and bedrock depth, slope, pH, organic matter, available water capacity (percent-weighted across components) and building-site ratings with shrink-s

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "farmland-soil-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoWGS84 latitude. Give lat with lon, or address.
lonNoWGS84 longitude.
useNoIntended use to rate. Omit to rate all four.
addressNoUS street address, geocoded by the US Census geocoder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does contribute real context: the authoritative data source (USDA NRCS), the geocoder used for addresses (US Census), and a computation detail (available water capacity percent-weighted across components). It omits what happens when a coordinate falls outside survey coverage, whether results are cached or rate-limited, and the text is truncated mid-word so the last attribute described is never finished.

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?

Front-loaded correctly with the tool's name and trigger, but the bulk is a single sprawling run-on sentence enumerating a dozen return attributes. Worse, the description is visibly truncated ("building-site ratings with shrink-s"), so the final clause delivers no information. Since no output schema exists, enumerating returns earns its place, but it should be restructured and completed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so describing returned fields is necessary and mostly done here. But the truncation leaves the output list incomplete, and the description never resolves the zero-required-parameter situation: what is returned or errored if the caller supplies neither coordinates nor address. Adequate, not complete.

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 schema already explains lat, lon, address and the use enum plus its default-when-omitted behavior. The description only echoes the lat/lon-or-address choice without adding format, precision, or fallback semantics. Baseline 3 is appropriate.

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?

Names a specific source and operation: reads the USDA NRCS soil survey at a point or US address and returns map unit, prime farmland class, drainage, hydric rating, water table and related attributes. The resource and scope are unmistakable. It loses a point only because there is no differentiation from sibling reporting tools, though none in the list appear to overlap.

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?

Implies the when: "Before buying, leasing or planting a US parcel." That gives a usable trigger and a geographic boundary (US only). However, it never states exclusions, prerequisites (one of lat/lon or address is needed though none are marked required), or any alternative tool to use for non-US parcels or for other land questions.

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.

Resources