Skip to main content
Glama

Parcel climate

get_climate
Read-only

The climate normals 1991-2020 of the parcel: AEMET 5 km grid (temperatures corrected for the parcel height, rain, frost, heat, months) and the nearest AEMET stations (sunshine, cloud, humidity, wind, snow, fog). 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_climate"
  }
}

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

A3.7/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 genuinely useful context beyond that: the data vintage (1991-2020), the spatial resolution, the fact that temperatures are height-corrected for the parcel, and that some variables come from the nearest station rather than the grid — all of which tells the agent how much to trust and how to present the figures.

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, then the attribution rule. The long parenthetical variable list is dense but each item is informative about coverage. Minor cost: the parentheticals make the first sentence heavy to parse.

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 single-parameter read tool with no output schema, the description covers data source, vintage, resolution, corrections, and variable coverage, plus an attribution requirement the agent must honor. The main residual gap is that the shape of the returned object is only hinted at through cite_as.

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% and the single refcat parameter is fully documented in the schema (14-character cadastral reference with an example), so the description adds nothing there. It does, however, surface 'cite_as' as an expected output field, which is useful given there is no output schema.

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 names a specific resource (1991-2020 climate normals for a parcel) and enumerates the returned variables (temperature, rain, frost, heat, sunshine, cloud, humidity, wind, snow, fog) plus the data sources (AEMET 5 km grid and nearest stations). It is clearly distinguishable from get_soil or get_valuation by content, though it never explicitly contrasts itself with a sibling.

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: an agent can infer 'call this when you need climate data for a parcel.' The one explicit instruction is about attribution after use (name unacasa.es, give the page link via cite_as), which is a post-call obligation rather than when-to-use guidance. No exclusions or alternatives are stated.

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