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

eea-climate-data-mcp

by bezilaszlo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_tables

List tables in a given database version to discover available European climate datasets from the EEA service, including GHG inventory and policies data.

Instructions

List tables in a database version.

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>"
    },
    "name": "list_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNolatest
databaseYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'List tables' and does not mention whether the operation is read-only, any permission requirements, or return behavior beyond what the output schema provides.

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?

The description is a single, concise sentence with no fluff. It conveys the core purpose efficiently, though it is minimal and does not earn extra points for explanatory richness.

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?

Even though the tool is simple and an output schema exists, the description is too terse to fully prepare an agent. It leaves ambiguities about what 'database version' means, how to specify the database, and whether all or only some tables are returned. With 18 sibling tools, more contextual differentiation would be expected.

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

Parameters1/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 explain what 'database' or 'version' mean, how they relate, or what values are expected. It adds no value beyond the parameter names and the default in the schema.

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'), the resource ('tables'), and the scope ('in a database version'). This distinguishes it from sibling tools like list_databases and list_versions, which list different entities.

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?

No guidance is provided about when to use this tool versus alternatives such as search_tables or describe_table. There is no mention of prerequisites, exclusions, or typical scenarios.

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