Skip to main content
Glama

Soilgrids

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON 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.6/5.0
Behavior4/5

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

Description adds value beyond annotations by disclosing latency ('may take several seconds') and output unit scaling ('real units'), which are not covered by the readOnlyHint and idempotentHint annotations. No contradiction.

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?

Two sentences, no fluff. Purpose and key details (source, resolution, units, latency) are front-loaded and efficiently communicated.

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?

Description adequately covers the tool's capabilities given its simplicity (no nested objects, no output schema). It explains the source, resolution, returned properties, and latency. Could specify output format more precisely but is sufficient.

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% with good descriptions for each parameter. The description provides an example of properties but does not add significant new meaning beyond the schema. Baseline score of 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?

The description clearly states the tool retrieves soil property values at any coordinate from ISRIC SoilGrids, listing specific properties. It does not explicitly differentiate from sibling tools like list_soil_properties or soil_classification, but the verb+resource is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. It mentions latency ('may take several seconds') but does not provide context on preferred scenarios or exclusion criteria.

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

All Soilgrids 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