Skip to main content
Glama

Soil Properties

soil_properties
Read-onlyIdempotent

Get soil property values at any coordinate from ISRIC SoilGrids (250m global grid), clay/sand/silt %, pH, organic carbon, nitrogen, cation exchange, bulk density, water content. Values are returned in real units (scaled from raw map units). Keyless; the SoilGrids API may take several seconds to respond.

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": {
      "latitude": 40.7128,
      "longitude": -74.006
    },
    "name": "soil_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoDepth interval (default "0-5cm"). Valid: "0-5cm", "5-15cm", "15-30cm", "30-60cm", "60-100cm", "100-200cm".
latitudeYesLatitude in decimal degrees (-90 to 90).
longitudeYesLongitude in decimal degrees (-180 to 180).
propertiesNoSoil property codes to query (default ["clay","sand","silt","phh2o","soc"]). Valid codes: clay, sand, silt (texture %), phh2o (pH in water), soc (soil organic carbon), nitrogen, cec (cation exchange capacity), bdod (bulk density), cfvo (coarse fragments), ocd (organic carbon density), wv0010/wv0033/wv1500 (volumetric water content at 10/33/1500 kPa).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "latitude": 40.7128,
      +    "longitude": -74.006
      +  },
      +  {
      +    "depth": "15-30cm",
      +    "latitude": -33.8688,
      +    "longitude": 151.2093,
      +    "properties": [
      +      "clay",
      +      "sand",
      +      "silt",
      +      "phh2o",
      +      "soc",
      +      "nitrogen",
      +      "cec"
      +    ]
      +  }
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish that the tool is read-only, idempotent, open-world, and non-destructive. The description adds meaningful behavior beyond them: values are returned in real units scaled from raw map units, no API key is required, and the SoilGrids API may take several seconds to respond.

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 two sentences and front-loads the core purpose, source, and resolution before covering units, keyless access, and latency. The property list is somewhat redundant with the schema's valid-code enumeration, but overall the wording is tight and purposeful.

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 four-parameter read-only lookup with full schema coverage and no output schema, the description covers source, resolution, unit scaling, authentication requirements, and latency. It does not describe the shape of the returned data, but otherwise provides enough context for an agent to call the 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?

Schema description coverage is 100%, so the schema already documents depth intervals and valid property codes. The description adds only a broad list of property families (texture, pH, organic carbon, etc.) and confirms that returned values are scaled to real units, which is useful but not a substitute for parameter-level detail.

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?

The description uses a specific verb and resource ("Get soil property values") and names the data source, resolution (250m global grid), and property families. It clearly indicates a coordinate-based point query, though it does not explicitly distinguish this from sibling tools like list_soil_properties or soil_classification.

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 phrase "at any coordinate" implies the primary usage context and "Keyless" establishes a prerequisite, but there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as list_soil_properties or soil_classification.

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.