Skip to main content
Glama

generate_site_analysis

Read-onlyIdempotent

Generate a branded multi-page PDF site analysis report for a specific location, covering power, transmission, gas, water, air permitting, fiber, latency, market, and tax.

Instructions

Use when a user wants a SHAREABLE, branded multi-page Site Analysis PDF for ONE lat/lon (a powered-land parcel, a candidate campus) — the polished client deliverable, not just a score. Example: "Make the Site Analysis PDF for this Carrier Mills parcel, 150 MW, for TON Infrastructure." — generate_site_analysis lat=37.694 lon=-88.65 capacity_mw=150 prepared_for="TON Infrastructure" prepared_by="Martone Advisors". Params: lat (-90 to 90, required), lon (-180 to 180, required), capacity_mw (target load MW, e.g. 50-500), prepared_for (client name on the cover), prepared_by (your firm — brands the report; defaults to DC Hub), latency_target (optional metro override; default = nearest real carrier hotel). Returns: {survey:{verdict, power/transmission, gas, water, air-permitting, fiber carriers, latency-to-nearest-carrier-hotel, market, tax}, pdf_report_url}. pdf_report_url is a ready-to-open link to download the branded 5-page PDF — no login needed, valid ~7 days; hand it to your human. For just the numeric suitability score (no PDF), use analyze_site instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoSite latitude in decimal degrees (-90 to 90, required), e.g. 37.694
lonNoSite longitude in decimal degrees (-180 to 180, required), e.g. -88.65
use_caseNoOptional workload descriptor to tailor the report, e.g. "AI training campus"
capacity_mwNoTarget power load for the build in megawatts (MW), e.g. 150 (typical 50-500)
prepared_byNoYour firm name that brands the report; defaults to DC Hub, e.g. "Martone Advisors"
prepared_forNoClient name printed on the report cover, e.g. "TON Infrastructure"
latency_targetNoOptional metro to measure latency against; default = nearest real carrier hotel
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds important behavioral details: PDF URL is ready-to-open, no login needed, valid ~7 days. No contradiction.

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?

Front-loaded with purpose, then example usage, parameter details, and return value. Every sentence is informative and earns its place; no fluff.

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?

Covers the return object structure (survey fields and pdf_report_url), explains PDF validity period, and handles the 7-parameter complexity well. No output schema needed given the description.

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% with descriptions for all 7 parameters. The description restates key parameters and adds examples, but doesn't significantly enhance meaning beyond the schema.

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 generates a 'SHAREABLE, branded multi-page Site Analysis PDF' for a specific lat/lon. It distinguishes itself from the sibling tool 'analyze_site' which only provides a numeric score.

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 states when to use ('Use when a user wants a SHAREABLE...') and provides a clear alternative: 'For just the numeric suitability score (no PDF), use analyze_site instead.' 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