Skip to main content
Glama
Sign In
eea-climate-data-mcp

eea-climate-data-mcp

by bezilaszlo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

query_sql

Execute validated SELECT queries on European climate data, returning rows and provenance from the EEA Discodata service.

Instructions

Execute a locally validated and bounded SELECT, returning rows and provenance.

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": {
      "sql": "<sql>"
    },
    "name": "query_sql"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlYes
pageNo
timeoutNo
max_rowsNo
page_sizeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It offers useful context: 'locally validated' indicates a pre-execution check, 'bounded' signals that limits apply, and 'returning provenance' tells the agent what the result will include. However, it does not disclose error handling, mutability implications, or permission requirements.

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 entire description is a single, front-loaded sentence that packs core behavior, validation, bounding, and return content. No wasted words, and the structure makes the purpose immediately clear.

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?

With five parameters, no annotations, and no schema descriptions, this short description is not enough. It lacks usage guidance, exclusions, and parameter details. The existence of an output schema covers return values, but the operational context is incomplete for an execution tool.

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%, and the description does not compensate. The phrase 'bounded' hints at some parameter constraints but does not explain the sql, page, timeout, max_rows, or page_size semantics. The agent must rely on parameter names alone, which is insufficient for a fully correct invocation.

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 clearly states the verb 'Execute' with resource 'a locally validated and bounded SELECT', and includes the output scope 'returning rows and provenance'. It is specific but does not explicitly distinguish from sibling tools like preview_rows or validate_sql, so it falls short of a 5.

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 description implies that this tool is for read-only SQL execution with validation and limits, but gives no explicit guidance on when to use it versus alternatives like validate_sql or explain_sql. No exclusions or alternative tool mentions are provided.

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

Deploy Server

Other Tools