eea-climate-data-mcp

Overview Schema Source Related Servers Discussions Admin

list_distinct_values

Lists distinct values from a column in an EEA climate database after validating the column against metadata, with an optional maximum row limit.

Instructions

List bounded distinct values after validating the column against metadata.

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": {
      "database": "<database>",
      "version": "<version>",
      "table": "<table>",
      "column": "<column>"
    },
    "name": "list_distinct_values"
  }
}

Input Schema

Name	Required	Description	Default
`table`	Yes
`column`	Yes
`version`	Yes
`database`	Yes
`max_rows`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It does disclose a meaningful behavioral trait: validation against metadata before listing values. However, it does not explain error behavior, rate limits, or other side effects. This is a minimal but nonzero addition.

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?

The description is a single sentence, 10 words, front-loaded with the core action. Every word earns its place with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the tool has 5 parameters with no param descriptions and no usage guidance. The description is too minimal to give an agent sufficient context for correct invocation, especially regarding what 'validating against metadata' entails and how max_rows behaves.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for parameter understanding. It adds no meaning for database, version, table, or max_rows; only the column concept is implicit. The 'bounded' hint is already in the schema via max_rows, so it adds little value.

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?

The description clearly states the action ('List bounded distinct values') and specifically targets a column, which distinguishes it from sibling tools like list_tables or preview_rows. The mention of validation adds specificity to the resource being operated on.

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?

There is no guidance on when to use this tool versus alternatives like query_sql or preview_rows. The description does not mention exclusions, prerequisites beyond validation, or context for selecting this tool over others.

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

Deploy Server