Skip to main content
Glama

save_site

Save a data-center site location to your DC Hub account with latitude, longitude, and optional details like market and target megawatts. Returns a site ID for future monitoring and alerts.

Instructions

Save a candidate data-center site to your DC Hub account to track it across sessions (FREE — just needs a key; call claim_free_key if you don't have one). Give lat + lon (plus optional name, state, market, target_mw, notes). Returns the saved site id. Pass market and DC Hub snapshots the site's DCPI baseline at save time, so every later list_saved_sites / get_changes shows how ITS score and verdict moved since you saved it. Builds a persistent shortlist an agent can revisit + monitor — after saving, pass the returned id to set_site_alert so DC Hub emails you when that site’s DCPI/capacity/nearby-facilities move (no re-checking). Try: save_site lat=39.04 lon=-77.48 name="Ashburn parcel" market=northern-virginia target_mw=100. Do NOT use to read back the shortlist (use list_saved_sites), download it (use export_dataset), or score a site (use score_facility); this WRITES one site to your account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoSite latitude in decimal degrees (-90 to 90), e.g. 39.04
lonNoSite longitude in decimal degrees (-180 to 180), e.g. -77.48
nameNoOptional label for the saved site, e.g. "Ashburn parcel"
notesNoOptional free-text notes to store with the saved site
stateNoUS state abbreviation for the site, e.g. VA
marketNoMarket slug (metro) the site belongs to, e.g. northern-virginia
target_mwNoTarget power load for the planned build in megawatts (MW), e.g. 100
Behavior4/5

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

Annotations are minimal (no readOnlyHint, etc.), so description carries the burden. It discloses that the tool writes a site, returns an id, snapshots DCPI when market is provided, and suggests set_site_alert for monitoring. No contradictions with annotations.

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 a single paragraph that front-loads purpose and key constraints. Every sentence adds value (purpose, requirements, effects, alternatives, example). Slightly long but justified by content.

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 write tool with no output schema, the description sufficiently covers what it does, what it returns, the flow with market and alerts, and prerequisites (key). Missing some details like idempotency but overall complete.

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?

Schema coverage is 100% but description adds context: implies lat/lon are effectively required, explains the effect of the market parameter (DCPI snapshot), and includes an example call. This goes beyond the schema descriptions.

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 it saves a site to a DC Hub account with lat/lon and optional fields, and explicitly distinguishes from siblings like list_saved_sites, export_dataset, and score_facility.

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 when to use (to save and track a site) and when not to (not for reading, downloading, scoring), provides alternative tool names, and includes a concrete example.

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