Skip to main content
Glama
Sign In

NetActuate

by com.netactuate
OverviewDiscussionsAdmin

Get one data center in full

get_data_center
Read-only

Returns everything NetActuate publishes about one facility: building specs, the facility's compliance certifications, physical security, connectivity and carrier access, power and cooling, the Looking Glass node id, the site-specific FAQs, whether VPU capacity is live there, and its netactuate.com URL. Use it once the site is known; to find sites, use list_data_centers or find_nearest_data_centers. Some cities have two facilities (the second is labelled '(extension)'): a city name returns the primary one in full and names the other in otherSitesInCity. A partial name matching several sites returns those candidates rather than a guess. Coordinates are the city's centre, not the facility's address.

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": {
      "location": "<location>"
    },
    "name": "get_data_center"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYesData center slug from list_data_centers (e.g. 'amsterdam-netherlands-datacenter') or city name, optionally with its country (e.g. 'Amsterdam', 'London, UK').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  3. Changed1 schema field changed
    • changedInput schema / properties / location / description
      Previous value: -"Data center slug (e.g. 'amsterdam-netherlands-datacenter') or city name (e.g. 'Amsterdam')."New value: +"Data center slug from list_data_centers (e.g. 'amsterdam-netherlands-datacenter') or city name, optionally with its country (e.g. 'Amsterdam', 'London, UK')."
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuinely new behavioral detail beyond them: a city name returns the primary facility in full while naming the sibling in otherSitesInCity, ambiguous partial names return candidates rather than resolving to a guess, and coordinates are the city centre rather than the facility address. These are resolution semantics an agent cannot infer from any structured field and are exactly the kind of gotcha that would otherwise cause misinterpretation of results.

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?

Front-loaded with purpose, then usage, then edge-case behavior; every sentence carries information and nothing is repeated from the schema. The long enumeration of returned field categories is dense but justified given there is no output schema; a tighter grouping could have trimmed a few words.

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?

With no output schema, the description takes on the job of describing return contents and does so (including the Looking Glass node id and VPU-capacity flag). Combined with the disambiguation rules and the coordinate caveat, an agent has everything needed to select and correctly interpret this single-parameter read tool.

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 parameter's own description already covers slug vs. city-name forms, so the baseline is 3. The description earns above baseline by documenting the runtime matching behavior for ambiguous inputs (multi-site city returns primary plus otherSitesInCity; partial name returns candidates), which is semantics the schema does not express.

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?

Opens with a specific verb and resource ('Returns everything NetActuate publishes about one facility') and enumerates the exact payload (specs, certifications, security, connectivity, power/cooling, Looking Glass node id, FAQs, VPU capacity, URL). This distinguishes it cleanly from list_data_centers and find_nearest_data_centers without opening any schema.

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?

Explicit routing: 'Use it once the site is known; to find sites, use list_data_centers or find_nearest_data_centers' names both alternatives and the precondition that selects them. It also sets expectations for two ambiguous-input cases (city with two facilities, partial name matching several sites), which tells the agent when the tool is still the right call and what it will get back.

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

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