Skip to main content
Glama

DC Blueprint data-centre intelligence

Tracked data-centre projects of one market

market_projects
Read-onlyIdempotent

Every data-centre project our pipeline tracker lists in one European market, latest stage first: name, stage, stated MW, the date it was last checked and its page. Needs a personal DC Blueprint key (Authorization: Bearer) from an account with a DC Blueprint licence or trial. The market costs 1 credit; the same list again in the calendar month costs nothing. A list longer than 25 projects comes in pages (the "page" argument). 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": "market_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOptional: the page of 25 projects, from 1.
marketYesA country or metro name, e.g. "Frankfurt", "Ireland", "the Netherlands".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial context beyond the readOnly/idempotent annotations: bearer-token auth requirements and licence gating, credit cost with a monthly free-repeat rule, sorting order (latest stage first), and pagination behaviour. This is exactly the operational information an agent needs before spending credits.

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 opening sentence is front-loaded and carries the core meaning, followed by cost/auth and then paging. The metro and country enumerations are long but functional given zero enum constraints in the schema — they earn their space, though a more compact phrasing could trim bulk.

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 two-parameter read tool with no output schema, the description covers auth, cost, caching, ordering, pagination and valid input values, plus the field set returned. Nothing an agent needs in order to invoke it correctly is missing.

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?

Goes well beyond the schema for the 'page' argument by disclosing the 25-per-page threshold and 1-based paging, and for 'market' by listing all valid metro and country values — critical since the schema has no enums. Only gap is the absence of any stated behavior for an unrecognised market value.

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?

Names a specific resource (every data-centre project tracked in one European market) and enumerates exactly what each record carries: name, stage, stated MW, last-checked date, page. That is distinguishable from an aggregate market overview by implication, but no sibling is named explicitly, so it stops 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 Guidelines4/5

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

Gives clear context for use: requires a DC Blueprint key from a licensed or trial account, costs 1 credit, and repeats within the same calendar month are free — which actively steers an agent to re-call rather than avoid. No explicit when-not-to-use or named alternative (e.g. versus data_centre_market_overview) is provided.

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