Skip to main content
Glama

Soil Classification

soil_classification
Read-onlyIdempotent

Get the World Reference Base (WRB) soil classification at a coordinate from ISRIC SoilGrids, the most probable soil class (e.g. Cambisols, Podzols) plus the top 5 classes with probabilities. Keyless; 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": 52.52,
      "longitude": 13.405
    },
    "name": "soil_classification"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeYesLatitude in decimal degrees (-90 to 90).
longitudeYesLongitude in decimal degrees (-180 to 180).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "latitude": 52.52,
      +    "longitude": 13.405
      +  }
      +]
  2. First observed

TDQS

A4/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, open-world), and the description adds genuinely new operational context: no API key is required and the call may take several seconds. It does not cover failure modes (e.g. ocean/no-data coordinates) or result determinism, so it stops short of a 5.

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?

A single front-loaded sentence: what it returns, where the data comes from, and the two operational caveats (keyless, slow). Nothing is redundant and no sentence could be removed without losing information.

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 correctly takes on the job of describing return values (most probable class plus top 5 probabilities), which is exactly what an agent needs. Remaining gaps are edge-case behavior for coordinates with no soil data and response format specifics, which are minor for a two-parameter read tool.

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% with both parameters fully documented including valid ranges, so the schema carries the parameter burden. The description only restates 'at a coordinate' and adds no format or coordinate-system detail beyond the schema.

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 and resource ('Get the World Reference Base (WRB) soil classification at a coordinate'), names the upstream source (ISRIC SoilGrids), and enumerates the payload (most probable class plus top 5 with probabilities). That is enough to separate it from soil_properties/list_soil_properties without opening any schema.

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 a coordinate' implies a single-point lookup, which is a usable usage signal, but the description never says when to pick this over the soil-properties siblings or what to do for multi-point/area queries. No explicit alternatives or exclusions are given.

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.