Skip to main content
Glama

AI Buildout Permits

Project Detail

project_detail
Read-onlyIdempotent

One data-center project in full: every named party and role with its ticker link (parent, method, confidence, evidence), on-site power (technology, maker, model, unit count, MW, with the quoted source line), the dated timeline of records, coordinates where stated, and each source's publisher, URL, retrieval time and file hash. Takes a project id from another tool, or a name.

Example questions:

  • "Who is behind Cipher's Barber Lake site?"

  • "What turbines are permitted at Project Matador?"

  • "Show the record for TX4"

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "project_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject id (e.g. tx-dc046706) or a name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is narrower and it delivers: it discloses that results include quoted source lines, retrieval timestamps and file hashes, which signals provenance-grounded output an agent can cite. It does not explain behavior when a name is ambiguous or a project id is not found, which is the main residual gap.

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 return payload is front-loaded in a single dense sentence followed by concrete example questions, with no filler or marketing language. The first sentence is long and comma-stacked, which slightly slows scanning, but every clause identifies a distinct returned field group rather than padding.

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?

With no output schema and a single parameter, the description correctly spends its budget describing the returned payload in detail, which is exactly what is needed here. What is missing is failure and ambiguity behavior — what happens on an unknown name or multiple name matches — which matters given the free-form 'or a name' input.

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% and the single parameter is already documented with an example id format, so the baseline is 3. The description adds real meaning by indicating the id typically comes from another tool's output, which tells the agent to chain calls rather than invent identifiers, and by confirming a human-readable name is equally acceptable.

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 opens with a specific verb-and-resource framing ('One data-center project in full') and then enumerates exactly what 'full' means: parties and roles with ticker links, on-site power specs, dated timeline, coordinates, and source provenance. Combined with 'Takes a project id from another tool, or a name', an agent can tell this is the single-record detail fetch that follows a search, distinct from siblings like find_projects or export.

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?

The phrase 'Takes a project id from another tool, or a name' establishes the workflow context (chain from a search result) and the accepted key forms, and the three example questions anchor realistic use cases. It stops short of explicit when-not guidance, e.g. 'use find_projects first if you only have a company name', so it is clear context rather than full routing.

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.