Skip to main content
Glama

DC Blueprint data-centre intelligence

Data-centre rules and deadlines by country

data_centre_rules
Read-onlyIdempotent

The national and EU rules for building and running a data centre in one European country (energy efficiency reporting, waste heat, permitting, grid), each with its status, who it applies to and the next date that matters, plus upcoming deadlines. Countries: Germany, France, Ireland, Netherlands, Italy, Spain, Sweden, Finland, Denmark, Poland, United Kingdom, Belgium, Czechia, Portugal, Switzerland, Norway, Greece, Austria, Hungary, Croatia, Lithuania, Latvia, Estonia, Romania, Bulgaria, Slovakia, Slovenia, Cyprus, Malta, Luxembourg, United States.

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": {
      "country": "<country>"
    },
    "name": "data_centre_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesA European country, e.g. "Germany".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is covered structurally. The description adds that results come with status, applicability and next dates plus upcoming deadlines, which tells the agent what the payload contains; it says nothing about coverage limits, freshness of rules, or behavior for unsupported countries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and content dimensions are front-loaded in the first clause, which is good. However, it is a single run-on sentence with a 32-item country tail that reads as data better suited to an enum, and the mixture of 'European country' framing with US inclusion makes the sentence internally muddy.

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 one-parameter, read-only lookup with no output schema, the description does the important work: it says what records are returned and what fields accompany each rule, and it lists the valid inputs. The main gap is the unsupported-country behavior and the geographic inconsistency, which an agent would need to know before calling.

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 country field already has an example, so the baseline is met. The enumeration of supported countries does add value since the schema defines no enum, but it also creates ambiguity against the stated scope of 'one European country' because the United States is in the list, leaving the agent unsure whether non-European inputs are valid.

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 the resource precisely (national and EU rules for building/running a data centre) and enumerates the content dimensions it returns (energy efficiency reporting, waste heat, permitting, grid, status, applicability, next date, upcoming deadlines). That clearly separates it from siblings like grid_connection_status or business_case_figures, though it never names those siblings explicitly.

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: the description suggests this is the tool for regulatory/deadline questions about a specific country, but it gives no explicit when-to-use/when-not-to-use guidance and no routing to alternatives such as grid_connection_status. The country list indirectly signals scope but not selection rules.

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