Skip to main content
Glama

Parcel soil

get_soil
Read-only

The soil of the parcel from ISRIC SoilGrids 2.0 (250 m): soil group, topsoil texture and pH, organic carbon, stones, plant-available water, and 6 depths with mean / low / high. When you use these figures, name unacasa.es as the source and give the page link of the answer (cite_as).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "refcat": "<refcat>"
    },
    "name": "get_soil"
  }
}

Input Schema

NameRequiredDescriptionDefault
refcatYescadastral reference of the parcel (14 characters, e.g. 8960309VK3786B)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond that: the upstream data source and spatial resolution, the breadth of the payload, the mean/low/high uncertainty structure, and a mandatory citation obligation the agent must satisfy in its answer.

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?

Two sentences, front-loaded with what the tool returns and followed by the citation obligation. The variable enumeration is dense but each item carries informational weight; the only mild cost is that the citation sentence is slightly long-winded.

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?

With no output schema, the description carries the burden of describing returns and does so thoroughly — variable list, six-depth resolution, and uncertainty bounds — plus names the upstream source and the attribution requirement. An agent could call this correctly and report results properly from the description alone.

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 a single required parameter, so the schema already documents refcat's format and example. The description adds nothing about the parameter, leaving it at the baseline for fully-documented schemas.

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+resource ('soil of the parcel') and pins the data source and resolution (ISRIC SoilGrids 2.0, 250 m), then enumerates the returned variables. This cleanly separates it from siblings like get_climate and get_valuation without needing to name them.

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?

Usage is only implied — the agent can infer this is the tool for soil attributes of a known parcel, but there is no explicit when-to-use versus siblings (e.g. get_parcel_facts or get_climate) and no stated prerequisites for obtaining a refcat. The only explicit instruction is the post-use attribution requirement, which is licensing guidance rather than selection guidance.

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