Skip to main content
Glama

DC Blueprint data-centre intelligence

Data-centre business-case figures for one market

business_case_figures
Read-onlyIdempotent

The inputs of a colocation data-centre business case for one European market: construction cost per MW, colocation prices per kW-month, electricity price, staff cost, guarding, property tax, exit yield, grid wait, permitting and grid charges, with low and high. Answers with no key: the market's build cost per MW with its low-to-high range, the date, the market page and its rank in the European Build Cost Index, free on every call. All figures need a personal DC Blueprint key (Authorization: Bearer) from an account with a DC Blueprint licence or trial. One market a call: every figure costs 5 credits, one figure (the "figure" argument) 1; the same answer again in the calendar month costs nothing. Markets: Amsterdam, Athens, Barcelona, Berlin, Bristol, Brussels, Central Scotland, Copenhagen, Dublin, Frankfurt, Helsinki, Lille, Lisbon, London, Lyon, Madrid, Marseille, Milan, Munich, Oslo, Paris, Prague, Rhineland, Rome, Stockholm, Vienna, Warsaw, Zagreb, Zaragoza, Zurich. Figures: Construction cost, Colocation price, retail, Colocation price, wholesale, Colocation price, large deals, Electricity price, Cost of a site employee, Guarding and monitoring, Property tax, Exit yield, Wait for a grid connection, Permitting, Grid connection charge, Customer substation. Each figure carries its trust level (high, medium or low).

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": "business_case_figures"
  }
}

Input Schema

NameRequiredDescriptionDefault
figureNoOptional: one figure only, e.g. "Construction cost" or "Exit yield" (1 credit). Leave it out for every figure of the market.
marketYesA business-case market, e.g. "Frankfurt", "Milan".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and the description usefully adds the credential requirement (personal DC Blueprint key with licence or trial via Bearer token), the per-figure credit cost, and per-figure trust levels. However, the billing model and free-tier details are stated twice in slightly different terms, and the description never says what happens on an unlicensed or out-of-credit call beyond implying it fails.

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?

The purpose and access costs are front-loaded, but the body is a run-on paragraph that mixes capability, licensing, billing, market enumeration and figure enumeration with repeated phrasing about credits and free repeats. The long enumerations do carry value as the schema has no enums, yet the framing sentences could be tightened substantially.

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 two-parameter, read-only lookup with no output schema, the description covers what an agent needs: the return contents (build cost per MW with low-to-high range, date, market page and European Build Cost Index rank), the authentication requirement, the credit economics and the trust-level caveat. The main residual gap is any hint about response shape or how missing figures are represented.

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?

Schema coverage is already 100%, so the baseline is 3; the description earns extra by supplying the closed value space the schema lacks (30 named markets and 15 named figures, e.g. "Grid connection charge", "Customer substation") and by tying the 'figure' argument to a lower credit cost. It still does not clarify matching behaviour, such as whether market names are case-sensitive or what happens with an unrecognised market.

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 a specific resource (colocation data-centre business-case inputs for one European market) and enumerates the figures returned, so an agent knows exactly what class of data this produces. It does not explicitly contrast itself with siblings like data_centre_market_overview or data_centre_rules, leaving some disambiguation to inference.

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?

It gives concrete operating guidance: one market per call, and use the 'figure' argument when only one figure is needed (1 credit vs 5 for the full set), plus the note that repeating the same answer within a calendar month is free. Auth prerequisites are stated. What is missing is an explicit statement of when to prefer a sibling tool over this one.

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