Skip to main content
Glama
Sign In

NetActuate

by com.netactuate
OverviewDiscussionsAdmin

List NetActuate data centers

list_data_centers
Read-only

Lists NetActuate's data centers (points of presence), filtered by any mix of region, country, certification, VPU capacity and free text; with no filter it returns every site with a page on netactuate.com, and dataCenterLocations, NetActuate's own total: the figure to quote for how many locations it has. Each result gives the slug, name, city, country, region, facilityCertifications (the facility's, not NetActuate's own: get_compliance_coverage has those) and netactuate.com URL. Use it for 'where does NetActuate have presence', 'anything in Asia', 'which European sites are SOC 2' or 'where can I get VPUs' (vpu: true). For one site in full use get_data_center; for the sites nearest a place, find_nearest_data_centers; for how many sites hold each certification, get_compliance_coverage. A region or country it does not recognise is explained in a note, so an empty list means no published site matches.

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": "list_data_centers"
  }
}

Input Schema

NameRequiredDescriptionDefault
vpuNotrue: only the locations where VPU capacity (NETINT video processing units, VPU-as-a-Service) is live today. Other locations are available for VPUs as a custom deployment.
queryNoWords that must all appear in the facility's published record (specs, carriers, FAQs), e.g. 'Equinix', 'liquid cooling', 'renewable'.
regionNoRegion. Accepts NetActuate's own names ('Europe', 'North America', 'Asia & Oceania', 'South America', 'Middle East & Africa') and common ways of asking: 'Africa', 'APAC', 'EMEA', 'LATAM', 'Middle East', 'Southeast Asia' all resolve.
countryNoCountry name, e.g. 'Germany', 'USA', 'United States', 'UK'. Matched exactly, not by substring.
certificationNoOnly return sites holding this certification, e.g. 'SOC 2', 'HIPAA', 'ISO 27001'. Naming several ('HIPAA and SOC 2') returns sites holding all of them; use 'or' for any of them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / vpu
      Added value: +{
+  "description": "true: only the locations where VPU capacity (NETINT video processing units, VPU-as-a-Service) is live today. Other locations are available for VPUs as a custom deployment.",
+  "type": "boolean"
+}
  2. 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"
  3. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  4. Changed1 schema field changed
    • changedInput schema / properties / certification / description
      Previous value: -"Only return sites holding this certification, e.g. 'SOC 2', 'HIPAA', 'ISO 27001', 'PCI-DSS'. Naming several ('HIPAA and PCI-DSS') returns sites holding all of them; use 'or' for any of them."New value: +"Only return sites holding this certification, e.g. 'SOC 2', 'HIPAA', 'ISO 27001'. Naming several ('HIPAA and SOC 2') returns sites holding all of them; use 'or' for any of them."
  5. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Free-text filter matched against the whole facility record."New value: +"Words that must all appear in the facility's published record (specs, carriers, FAQs), e.g. 'Equinix', 'liquid cooling', 'renewable'."
  6. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Although annotations already mark this as read-only, non-destructive, and closed-world, the description adds substantial behavioral context: no-filter returns every published site plus dataCenterLocations, each result includes specific fields, facilityCertifications belongs to the facility rather than NetActuate, and unrecognized regions are explained in a note. This is exactly the kind of return-set and edge-case behavior an agent needs beyond the annotations.

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 purpose and scope are front-loaded in the first sentence, and the sibling routing follows naturally. It is dense with semicolons and parentheticals, but the details are useful and there is little obvious filler.

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 fills the gap by naming the result fields, explaining the dataCenterLocations total, clarifying certification ownership, and covering empty-result behavior. Given five optional parameters and several sibling tools, this is complete enough for correct invocation.

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%, and the schema already documents vpu, query, region, country, and certification with examples and matching rules. The description reinforces the filter mix and vpu: true use case, but it does not add much parameter semantics beyond what the schema already provides.

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 states a specific verb and resource ('Lists NetActuate's data centers') and immediately defines scope as points of presence with optional filters. It clearly distinguishes this bulk/list tool from get_data_center, find_nearest_data_centers, and get_compliance_coverage.

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?

It gives explicit use cases ('where does NetActuate have presence', 'anything in Asia', 'which European sites are SOC 2', 'where can I get VPUs') and routes the agent to alternatives for single-site detail, nearest-site lookup, and certification counts. It also explains the no-filter default and empty-result meaning.

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