Skip to main content
Glama
Sign In

Dchub

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Dchub Get News

dchub_get_news
Read-onlyIdempotent

Curated data-center industry news (DC Hub) from 40+ trade sources (DCD, Data Center Knowledge, Data Center Frontier, Capacity Media, etc.), refreshed every 30 min. Filter by category (deals/permits/outages/policy/AI), source, or date range. Keyless calls return a preview.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 5,
      "category": "AI"
    },
    "name": "dchub_get_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return (1-500; default varies)
queryNoFree-text keyword, e.g. "Stargate" or "interconnection queue"
sourceNoRestrict to one trade source, e.g. DCD, "Data Center Frontier"
date_toNoLatest published date, ISO-8601 (YYYY-MM-DD)
categoryNoNews topic filter, e.g. deals, permits, outages, policy, AI
date_fromNoEarliest published date, ISO-8601 (YYYY-MM-DD)

Output Schema

NameRequiredDescriptionDefault
resultNo
sourceNo
previewNo
preview_noticeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and open-world, so the bar is lower; the description still adds real value with the 30-minute refresh cadence and the keyless-preview limitation, both of which change how an agent interprets results. It stops short of saying how large a preview is or whether pagination exists.

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?

Three sentences: identity first, then filtering, then the keyless caveat. No filler, and the most decision-relevant facts are front-loaded.

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?

With an output schema present and 100% parameter coverage, the description only needs to frame purpose, freshness, and access tiers — which it does. The one loose end is what 'preview' concretely means (count/fields omitted), leaving minor ambiguity for an agent planning around limited credentials.

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%, so all six parameters are already documented with examples. The description restates the category taxonomy (deals/permits/outages/policy/AI) and the source/date filters without adding syntax or edge-case guidance beyond the schema — the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource ('curated data-center industry news') with concrete provenance (40+ named trade sources) and freshness (refreshed every 30 min). An agent can distinguish this from dchub_get_grid_data, dchub_get_market_intel, and dchub_search_facilities without opening any schema.

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?

Explains how to narrow results (category, source, or date range) and warns that keyless calls return a preview, which materially affects expectations. It does not, however, state when to prefer this over sibling dchub_ tools or mention any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Dchub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources