Skip to main content
Glama

DC Blueprint data-centre intelligence

Search DC Blueprint

search_dcblueprint
Read-onlyIdempotent

Search DC Blueprint's pages: the four steps, the European market pages, the trackers (data-centre pipeline, grid connections, tenders, substation headroom), the Insights articles, the glossary, the operator pages and the facility pages. Returns up to 5 pages, best match first, with title, date, link and summary.

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": {
      "query": "<query>"
    },
    "name": "search_dcblueprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look for, e.g. "PUE benchmarks", "fibre latency London Frankfurt".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety and side-effect profile is fully covered. The description goes beyond that by disclosing the result contract: at most 5 pages, ranked best-match-first, each with title, date, link and summary. That ranking and result-cap information is genuinely useful for an agent deciding whether one call is sufficient or whether to refine the query.

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

Conciseness5/5

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

Two sentences, zero filler, with the search target and covered content front-loaded before the return contract. Every clause carries information: the page categories define recall expectations, and the second sentence defines the result cap, ordering and fields.

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 search tool with complete annotation coverage, this is nearly everything an agent needs: scope, ranking, result cap and returned fields are all stated. The absence of an output schema is compensated by the enumerated return fields. Only the alternative-selection guidance against the sibling data tools is missing.

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 description coverage is 100% and the single 'query' parameter already carries its own natural-language explanation with two example strings. The description's content enumeration indirectly hints at what is searchable, which helps frame queries, but it adds no syntax, matching behaviour or ranking-control detail beyond the schema. Baseline 3 is appropriate when the schema does the work.

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 opens with a specific verb and resource ('Search DC Blueprint's pages') and then enumerates the covered content classes: the four steps, European market pages, four named trackers, Insights articles, glossary, operator and facility pages. That enumeration makes the tool's scope unmistakable and clearly broader than the narrow data lookups implied by siblings like grid_connection_status or business_case_figures. It stops short of naming a sibling tool as the alternative, which keeps it out of the top band.

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: an agent can infer this is the general keyword search across the site and the siblings are single-topic data endpoints, but the description never states when to prefer this tool over those siblings or when not to use it. There are no prerequisites or exclusions given. Adequate for a simple search endpoint, but the routing logic is left to inference.

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