Spain Open Data MCP

Chart

chart

Read-onlyIdempotent

Draw a PNG of Spanish place data—opportunity rankings, income by district, age pyramids, or population trends—and return the image, text, and sources.

Instructions

Draw a chart (PNG) of a tool result: an opportunity ranking with ranges, income by district, an age pyramid or a population trend. Returns the image, the same text and sources as the underlying tool, and a source line on the image. If drawing fails the text still comes back.

Input Schema

Name	Required	Description	Default
`kind`	Yes	'opportunity' (needs category; ranks areas within the place), 'income' (by district or tract), 'age_pyramid' or 'population_trend'.
`place`	Yes	Place name or INE code: municipality ('Valladolid' or '47186'), province ('41'; a bare name like 'Sevilla' means the city), autonomous community ('Cataluña' or 'CA09'), district ('4718603') or census tract ('4718603012'). 'Name, Province' picks between same-named towns.
`category`	No	Business category, for kind 'opportunity'.
`sub_areas`	No	For 'income': districts or tracts.	district

Output Schema

Name	Required	Description
`data`	Yes
`checks`	No
`sources`	Yes
`confidence`	Yes	Lowest confidence across inputs: high, medium or low. Never state a conclusion more strongly than this.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.1Oct 17, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower. The description still adds real value: the output is an image plus the underlying text and sources, a source line is stamped on the image, and it degrades gracefully by returning text if drawing fails.

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, front-loaded with the action and output type, with the failure-mode caveat last. Every clause earns its place and nothing is padded.

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 a full output schema and 100% parameter coverage, the description need not restate return values or param formats, and it still covers output composition and failure behavior. Only the when-to-use routing is thin, which is a minor gap.

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%, including detailed enum semantics and place-code formats, so the schema carries the parameter burden. The description adds no format or syntax detail beyond what the schema already documents; baseline 3 is appropriate.

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 ('Draw a chart (PNG)') and enumerates the exact four chart kinds that match the kind enum, so an agent immediately understands the scope. No sibling tool draws images, so this is clearly differentiated from income, demographics, etc.

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 'of a tool result' implies this wraps/enriches the data tools (income, opportunity), but the description never explicitly says when to prefer a chart over the bare numeric tool, nor names alternatives or exclusions. Usage is inferable but not stated.

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

Deploy Server