Skip to main content
Glama

Scrutica

by io.github.davidgringras
OverviewDiscussionsAdmin

scrutica_get_facility

Read-only

Fetch complete details for a single Scrutica facility by canonical ID. Returns: roles[] — each organisation the record names, under the relationship its own source ESTABLISHES (site owner, site operator, AI hardware owner, or another relationship such as PeeringDB listing holder, lessee, developer), with the reason, source URL, quote and authority tier; withheld_roles[] — recorded attributions the cited source does not establish, with the reason; then country, power capacity (MW), GPU inventory (where disclosed), location (lat/lng), facility type, status, data_source, source_url, is_estimated flags, and any logged data-quality flags (cross-source divergence investigations). present_inventory is Scrutica's partition-by-partition compute evidence (the verdict the facility page, threshold table and query tools use): each accelerator partition admitted at its cited dense FP16 rate or held with a reason; one held partition withholds the facility figure. facility.peak_pflops_fp16 and h100_equivalent_gpus are the record's catalogue scalars, a different basis. Describe an organisation as the site's owner ONLY where roles[] names it "Site owner"; a recorded organisation is not by itself evidence of title or operation. For BIS Entity List designations tied to an organisation recorded at the facility, look it up via scrutica_query_export_controls — this tool does not compute ownership-chain BIS exposure. Resolve facility IDs first via scrutica_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoAlias for facility_id.
entity_idNoAlias for facility_id.
facility_idNoREQUIRED. Canonical Scrutica facility ID. Format: 'fac-<slug>' (e.g. 'fac-tsmc-arizona-fab21-p2', 'fac-tsmc-fab-18'). Resolve via scrutica_search first — do NOT guess slugs. Optional in the schema only so the aliases below can stand in; supply exactly one of these.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / entity_id
      Added value: +{
+  "description": "Alias for facility_id.",
+  "type": "string"
+}
    • changedInput schema / properties / facility_id / description
      Previous value: -"Canonical Scrutica facility ID. Format: 'fac-<slug>' (e.g. 'fac-tsmc-arizona-fab21-p2', 'fac-tsmc-fab-18'). Resolve via scrutica_search first — do NOT guess slugs."New value: +"REQUIRED. Canonical Scrutica facility ID. Format: 'fac-<slug>' (e.g. 'fac-tsmc-arizona-fab21-p2', 'fac-tsmc-fab-18'). Resolve via scrutica_search first — do NOT guess slugs. Optional in the schema only so the aliases below can stand in; supply exactly one of these."
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Alias for facility_id.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "facility_id"
-]
  2. Changed1 schema field changed
    • changedInput schema / properties / facility_id / description
      Previous value: -"Canonical Scrutica facility ID (e.g. 'epoch-dc-001')"New value: +"Canonical Scrutica facility ID. Format: 'fac-<slug>' (e.g. 'fac-tsmc-arizona-fab21-p2', 'fac-tsmc-fab-18'). Resolve via scrutica_search first — do NOT guess slugs."
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

While annotations declare readOnlyHint=true, the description goes far beyond that. It explains the nuanced semantics of roles[] (source-established relationships), withheld_roles[], present_inventory vs. catalogue scalars, and clarifies that a recorded organisation is not evidence of title. This rich behavioral detail helps the agent interpret results correctly and avoid common misconceptions.

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?

The description is dense but well-structured. It front-loads the core purpose, then enumerates return fields, then adds critical clarifications and usage notes. Every sentence contributes value—no fluff or redundancy. The length is justified by the complexity of the data returned.

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 the lack of an output schema, the description thoroughly documents the return structure (roles, withheld_roles, inventory, scalars, etc.) and the semantics of each. It also addresses the prerequisite (ID resolution) and the tool's limitations. An agent has everything needed to call it correctly and interpret the response accurately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even with 100% schema coverage, the description adds crucial parameter guidance: it explains that facility_id is required, gives the format pattern ('fac-<slug>'), clarifies the alias mechanism, and mandates that exactly one of the three aliases must be supplied. This is essential practical information that the schema itself does not convey.

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 precise verb+resource: 'Fetch complete details for a single Scrutica facility by canonical ID.' It clearly distinguishes from siblings by explicitly stating it does not compute BIS exposure (unlike scrutica_query_export_controls) and that it requires a resolved ID (unlike scrutica_search). The purpose is unambiguous and well-separated.

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?

Provides explicit usage instructions: 'Resolve facility IDs first via scrutica_search' and warns 'do NOT guess slugs.' It also directs BIS-related queries to scrutica_query_export_controls and clarifies that this tool does not handle ownership-chain BIS exposure. This gives clear when-to-use and when-not-to-use guidance, plus a direct pointer to the alternative.

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

All Scrutica 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