Skip to main content
Glama
Sign In

DC Hub

by cloud.dchub
OverviewDiscussionsAdmin

Tax Incentives

get_tax_incentives
Read-onlyIdempotent

Use this when the user asks what tax incentives a US state gives data centers — the data-center tax-incentive packages by US state that drive where capex lands. Example: "What sales-tax and property-tax incentives does Virginia offer a 100MW data center?" — get_tax_incentives state=VA. Params: state (2-letter US code; required). Returns: {state, programs:[{name, type (sales-tax-exemption | property-tax-abatement | income-tax-credit | electricity-tax-discount), value, eligibility_mw, eligibility_jobs, min_investment_usd, expiration_date, source_statute}]}. Cite the statute with attribution to DC Hub (CC-BY-4.0). Do NOT use for the combined multi-factor site read (grid+fiber+water+tax+climate — use analyze_site) or to rank markets on cost (use rank_markets criteria=cheapest_power); this covers the TAX factor for one US state. state is a US state code (e.g. VA); omit for the 50-state overview. Program detail needs a paid key (human_url).

Input Schema

NameRequiredDescriptionDefault
stateNoUS state abbreviation (required), e.g. VA, TX, AZ

Output Schema

NameRequiredDescriptionDefault
dataNo
countNo
stateNo
statusNo
cite_asNo
last_updatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedOutput schema / properties / _entity
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / _front_door
      Removed value: -{
-  "type": "object"
-}
    • removedOutput schema / properties / _return_loop
      Removed value: -{
-  "type": "object"
-}
    • removedOutput schema / properties / citation
      Removed value: -{}
    • removedOutput schema / properties / provenance
      Removed value: -{
-  "type": "object"
-}
    • removedOutput schema / properties / quota
      Removed value: -{
-  "type": "object"
-}
    • removedOutput schema / properties / site_evaluation_handoff
      Removed value: -{}
  2. Changed30 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -{}New value: +true
    • removedOutput schema / properties / _entity / description
      Removed value: -"Payload class (facility|market|iso_grid|queue_results|deal|report|response); branch on it."
    • removedOutput schema / properties / _front_door / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / _front_door / description
      Removed value: -"First-tool hint: plan_query(intent) returns the ordered plan."
    • removedOutput schema / properties / _front_door / properties
      Removed value: -{}
    • removedOutput schema / properties / _return_loop / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / _return_loop / description
      Removed value: -"Next-session delta call (get_changes)."
    • removedOutput schema / properties / _return_loop / properties
      Removed value: -{}
    • removedOutput schema / properties / citation / anyOf
      Removed value: -[
-  {
-    "additionalProperties": {},
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "type": "string"
-  }
-]
    • removedOutput schema / properties / citation / description
      Removed value: -"How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string."
    • removedOutput schema / properties / cite_as / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedOutput schema / properties / cite_as / description
      Removed value: -"Ready-made attribution line"
    • removedOutput schema / properties / count / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • removedOutput schema / properties / count / description
      Removed value: -"Rows returned in THIS response"
    • removedOutput schema / properties / data / anyOf
      Removed value: -[
-  {
-    "items": {
-      "additionalProperties": {},
-      "properties": {},
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedOutput schema / properties / data / description
      Removed value: -"Incentive programs for the state"
    • removedOutput schema / properties / last_updated / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedOutput schema / properties / last_updated / description
      Removed value: -"Incentive table last reviewed"
    • removedOutput schema / properties / provenance / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / provenance / description
      Removed value: -"Source, method, as_of, verification_counts, license, cite_as; quote it when citing."
    • removedOutput schema / properties / provenance / properties
      Removed value: -{}
    • removedOutput schema / properties / quota / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / quota / description
      Removed value: -"Caller quota state (remaining calls, tier)."
    • removedOutput schema / properties / quota / properties
      Removed value: -{}
    • removedOutput schema / properties / site_evaluation_handoff / anyOf
      Removed value: -[
-  {
-    "items": {
-      "additionalProperties": {},
-      "properties": {},
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "additionalProperties": {},
-    "properties": {},
-    "type": "object"
-  }
-]
    • removedOutput schema / properties / site_evaluation_handoff / description
      Removed value: -"Follow-up calls [{tool, parameters, why}] when the payload carries coordinates."
    • removedOutput schema / properties / state / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedOutput schema / properties / state / description
      Removed value: -"State queried"
    • removedOutput schema / properties / status / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedOutput schema / properties / status / description
      Removed value: -"Serving status"
  3. Added
  4. Removed
  5. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  6. Changed5 schema fields changed
    • removedOutput schema / properties / citation / additionalProperties
      Removed value: -{}
    • addedOutput schema / properties / citation / anyOf
      Added value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "string"
+  }
+]
    • changedOutput schema / properties / citation / description
      Previous value: -"Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload."New value: +"Machine-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."
    • removedOutput schema / properties / citation / properties
      Removed value: -{}
    • removedOutput schema / properties / citation / type
      Removed value: -"object"
  7. Changed1 schema field changed
    • addedOutput schema / properties / _front_door
      Added value: +{
+  "additionalProperties": {},
+  "description": "In-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan.",
+  "properties": {},
+  "type": "object"
+}
  8. Changed5 schema fields changed
    • removedOutput schema / properties / site_evaluation_handoff / additionalProperties
      Removed value: -{}
    • addedOutput schema / properties / site_evaluation_handoff / anyOf
      Added value: +[
+  {
+    "items": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  }
+]
    • changedOutput schema / properties / site_evaluation_handoff / description
      Previous value: -"Pre-built follow-up call (analyze_site / get_water_risk args) when the payload carries coordinates."New value: +"Pre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries."
    • removedOutput schema / properties / site_evaluation_handoff / properties
      Removed value: -{}
    • removedOutput schema / properties / site_evaluation_handoff / type
      Removed value: -"object"
  9. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "DC Hub envelope: structuredContent mirrors the JSON payload in content[0].text — tool-specific data fields ride at the top level alongside these envelope keys.",
+  "properties": {
+    "_entity": {
+      "description": "Payload class discriminator (e.g. facility|market|iso_grid|queue_results|deal|report|response) — branch on this before parsing the rest.",
+      "type": "string"
+    },
+    "_return_loop": {
+      "additionalProperties": {},
+      "description": "Suggested next-session delta call (get_changes since=24h) so you pull only what changed.",
+      "properties": {},
+      "type": "object"
+    },
+    "citation": {
+      "additionalProperties": {},
+      "description": "Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload.",
+      "properties": {},
+      "type": "object"
+    },
+    "provenance": {
+      "additionalProperties": {},
+      "description": "Collection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing.",
+      "properties": {},
+      "type": "object"
+    },
+    "quota": {
+      "additionalProperties": {},
+      "description": "Caller quota state (remaining calls, tier) when available.",
+      "properties": {},
+      "type": "object"
+    },
+    "site_evaluation_handoff": {
+      "additionalProperties": {},
+      "description": "Pre-built follow-up call (analyze_site / get_water_risk args) when the payload carries coordinates.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  10. Changed1 schema field changed
    • addedInput schema / properties / state / description
      Added value: +"US state abbreviation (required), e.g. VA, TX, AZ"
  11. Changed5 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / state / default
      Removed value: -""
    • removedInput schema / properties / state / title
      Removed value: -"State"
    • removedInput schema / title
      Removed value: -"get_tax_incentivesArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_tax_incentivesOutput",
-  "type": "object"
-}New value: +null
  12. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_tax_incentivesOutput",
+  "type": "object"
+}
  13. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_tax_incentivesOutput",
-  "type": "object"
-}New value: +null
  14. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_tax_incentivesOutput",
+  "type": "object"
+}
  15. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_tax_incentivesOutput",
-  "type": "object"
-}New value: +null
  16. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real behavioral context beyond them: program detail requires a paid key (human_url), results are sourced with an attribution obligation (cite statute, DC Hub CC-BY-4.0), and the 50-state overview path when state is omitted. No annotation is contradicted.

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?

Front-loads the use case and example, then exclusions, then auth notes — good ordering. It is somewhat dense and the 'Returns:' block enumerates fields already present in the output schema, which is length that does not earn its place, but overall it is information-rich rather than padded.

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?

Given an output schema exists, the definition is more than complete: it covers purpose, triggering example, explicit exclusions, auth/paywall requirements, and attribution obligations. The only flaw is the required-vs-omit inconsistency for state, which is minor against an otherwise exhaustive definition.

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% for the single parameter, so the baseline is 3; the description mostly restates the schema ('2-letter US code'). It does add the 'omit for the 50-state overview' behavior, but that conflicts with the schema's '(required)' label and the zero required parameters, creating mild confusion rather than clarity.

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 verb and resource — data-center tax-incentive packages by US state — and frames the domain value ('drive where capex lands'). It explicitly distinguishes itself from the two nearest siblings (analyze_site for the combined read, rank_markets for cost ranking), so an agent can route without opening the schema.

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?

Gives a concrete triggering example ('What sales-tax and property-tax incentives does Virginia offer a 100MW data center?') plus explicit when-not clauses naming the correct alternatives (analyze_site, rank_markets criteria=cheapest_power). The scope boundary 'this covers the TAX factor for one US state' removes ambiguity.

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

All DC Hub 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