Skip to main content
Glama

DC Blueprint data-centre intelligence

Data-centre market overview (Europe)

data_centre_market_overview
Read-onlyIdempotent

Dated overview of a European data-centre market: how many data-centre projects of 500 kW or more our pipeline tracker lists and how many are permitted or being built, the facility power by stage (IT load and MVA converted, marked ≈), who develops the most of them, whether new grid connections are paused, rationed or conditional in that country, the grid carbon intensity and power price this hour, how many operating data-centre sites we track there (at least), its first three tracked projects, a dated one-sentence reading of the market with a class word for land, permitting, grid connection, power, cooling and more (words, no figures), and how many data-centre rules apply. Use for questions like "data centres in Germany", "Frankfurt data centre market", "who is building data centres in Spain". Metros: London, Frankfurt, Paris, Amsterdam, Dublin, Milan, Madrid, Central Scotland, Zaragoza, Helsinki, Zurich, Berlin, Athens, Lille, Lyon, Rhineland, Rome, Warsaw, Barcelona, Copenhagen, Lisbon, Oslo, Stockholm, Zagreb, Bristol, Brussels, Marseille, Munich, Prague, Vienna. Countries: United Kingdom, Germany, Italy, Spain, France, Finland, Norway, Netherlands, Ireland, Poland, Sweden, Greece, Switzerland, Denmark, Portugal, Belgium, Czechia, Romania, Bulgaria, Croatia, Estonia, Austria, Lithuania, Slovakia, Hungary, Latvia, Luxembourg, Slovenia.

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": {
      "market": "<market>"
    },
    "name": "data_centre_market_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketYesA country or metro name, e.g. "Frankfurt", "Ireland", "the Netherlands".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. Beyond that the description adds genuine behavioural context: the data is dated, MVA values are converted and marked with ≈, site counts are a floor ("at least"), and carbon intensity and power price are explicitly "this hour" — signalling a time-sensitive snapshot rather than a live feed.

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?

Purpose and use cases are front-loaded, and the long sentence is dense but earns most of its length by previewing return content in the absence of an output schema. The ~58-name metro/country enumeration is a large block that could have been trimmed or grouped, and it slightly buries the usage examples that precede it.

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

Completeness5/5

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

For a high-complexity aggregate tool with no output schema, the description covers return contents, argument scope, freshness cues (dated, this hour) and precision caveats (≈ conversions, minimum site counts). An agent can decide to call it and interpret the answer without further documentation.

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

Parameters4/5

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

With 100% schema coverage on a single parameter the baseline would be 3, but the description goes further by enumerating 30 accepted metros and 28 accepted countries, which lets the agent form a valid value without guessing or triggering error recovery. It does not clarify fuzzy matching, casing, or whether unfamiliar place names fail or degrade.

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 opening clause, "Dated overview of a European data-centre market," gives a specific verb and resource, and the rest of the sentence enumerates exactly what the overview bundles (pipeline counts, power by stage, developers, grid connection status, carbon intensity, price, site counts, rules). It is unmistakably distinguishable from a single-dataset sibling, but it never names a sibling or states that this is the aggregate/composite entry point versus drilling into one dataset.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use for questions like 'data centres in Germany', 'Frankfurt data centre market', 'who is building data centres in Spain'" gives concrete triggering questions, and the appended metro/country lists effectively define the accepted scope of the argument. There is no when-not guidance and no mention of the sibling tools an agent might prefer for a narrower question.

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