Skip to main content
Glama
azmartone67

DC Hub — Data Center & Energy Intelligence

by azmartone67
OverviewSchemaRelated ServersScoreDiscussions(1)
JavaScript
Remote

Gas Index (DCGI)

get_gas_index
Read-onlyIdempotent

Evaluate data center natural-gas suitability with a per-state Data Center Gas Index. Withdrawn due to defects; use get_gas_intelligence for gas data.

Instructions

Data Center Gas Index (DCGI) — the per-US-state natural-gas suitability score. ★ WITHDRAWN 2026-08-08: this tool no longer returns a score. The backend returns an unavailable_reason naming the defects — the 20-point interstate-share term compared a lowercase literal against capitalised EIA TYPEPIPE values and scored ~0 for all 53 published states, and the 40%-weighted cost term was a hardcoded constant for nine states including Texas (published at DCGI 68.0, rank #3, GAS-ADVANTAGED off that constant). DO NOT quote a cached DCGI figure. Use get_gas_intelligence for the natural-gas pipeline, operator and parent-midstream data, which is unaffected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return (1-500; default varies by tool)
stateNoUS state abbreviation for a single-state DCGI breakdown, e.g. TX, VA, AZ; omit for the national ranking

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
quotaNoCaller quota state (remaining calls, tier) when available.
_entityNoPayload class discriminator (e.g. facility|market|iso_grid|queue_results|deal|report|response) — branch on this before parsing the rest.
citationNoMachine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload. Normally an OBJECT {source, url, license, cite_as, retrieved_at}; a bare string is accepted and carries the attribution line itself.
provenanceNoCollection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing.
_front_doorNoIn-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan.
_return_loopNoSuggested next-session delta call (get_changes since=24h) so you pull only what changed.
site_evaluation_handoffNoPre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries.

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

The description discloses far more than the annotations provide. It reveals that the tool is withdrawn, returns an `unavailable_reason`, details the specific scoring defects (e.g., case-sensitive comparison, hardcoded constant for Texas), and warns about stale cached figures. This is rich behavioral context beyond readOnly/idempotent hints.

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 description is longer than typical but every sentence carries essential information: withdrawal status, reason, warning, and alternative. It is front-loaded with the withdrawal notice, making the critical fact immediately visible. Slightly verbose in the defect details, but each detail supports the 'do not use' guidance.

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?

With an output schema present, the description does not need to explain return values. It fully explains the current behavior (unavailable_reason), warns about cached data, and points to the unaffected sibling. The description is complete for an agent to decide not to invoke this tool and to choose the correct alternative.

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?

The input schema already provides 100% parameter descriptions for `limit` and `state`. The description does not add meaning beyond the schema; it mentions the per-state vs national ranking context, but that is already implied by the schema's `state` description. 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?

The description clearly states the tool's role as the per-US-state natural-gas suitability score and immediately notes it is withdrawn, now returning an `unavailable_reason` instead of a score. It also distinguishes this tool from `get_gas_intelligence` by name, making its purpose unambiguous.

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

Usage Guidelines5/5

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

Explicitly tells the agent when NOT to use this tool ('DO NOT quote a cached DCGI figure') and directs to the alternative: 'Use get_gas_intelligence for the natural-gas pipeline, operator and parent-midstream data, which is unaffected.' This is direct, actionable guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/azmartone67/dchub-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server