Skip to main content
Glama

AI Buildout Permits

Equipment Tracker

equipment_tracker
Read-onlyIdempotent

On-site generation at data-center campuses as the records state it: turbine or engine maker, model, unit count, unit and total MW, status and planned online date, each with its quoted source line; summarized by maker and model. Rows whose record names no maker say so. Requires a subscription.

Example questions:

  • "Which turbine makers appear in data-center air permits?"

  • "How many Siemens SGT-800s are permitted?"

  • "Planned gas generation at data-center campuses in Texas"

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "equipment_tracker"
  }
}

Input Schema

NameRequiredDescriptionDefault
makerNoe.g. GE Vernova, Siemens Energy, Mitsubishi, Caterpillar, Bloom.
modelNoe.g. 7HA.02, SGT-800, FT8.
stateNoTwo-letter US state code, e.g. TX, VA, OH.
technologyNoe.g. gas turbine, reciprocating engine, fuel cell, combined cycle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds value beyond that: it discloses a subscription requirement, that each row carries a quoted source line, that output is summarized by maker and model, and that records naming no maker are labelled explicitly. Remaining gaps are about result size/pagination, which are minor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence is a dense comma-chained fragment that front-loads field enumeration before stating what the tool actually returns. The example questions earn their place, but the opening sentence could be recast as a short verb-first lead plus a field list without losing information.

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?

There is no output schema, so the description carries the return-value burden, and it does so reasonably: record fields, source attribution, per-maker/model aggregation, and explicit handling of unknown makers. It stops short of stating result shape (list vs. aggregate counts) or volume limits, which for a read-only query tool is a small residual gap.

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 description coverage is 100%, so all four filters are documented in the schema itself with examples, and the baseline of 3 applies. The description adds only marginal semantics ('Rows whose record names no maker say so' clarifies how the maker filter interacts with missing data) and says nothing about how filters combine or are matched.

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

Purpose4/5

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

The description names the resource precisely: on-site generation records at data-center campuses, broken out by maker, model, unit count, unit/total MW, status and planned online date. That is far more specific than the title 'Equipment Tracker' and lets an agent distinguish it from project- or company-level siblings. It lacks an explicit verb ('returns'/'lists'), so the purpose must be inferred from a fragment rather than read directly.

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?

Three sample questions ('Which turbine makers appear in data-center air permits?', 'How many Siemens SGT-800s are permitted?', 'Planned gas generation at data-center campuses in Texas') give concrete, unambiguous use contexts that map onto the maker/model/state filters. No exclusions or sibling alternatives are named, so an agent is not told when a different tool would be preferable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.