Skip to main content
Glama
Sign In

NetActuate

by com.netactuate
OverviewDiscussionsAdmin

List internet exchange presence

list_internet_exchanges
Read-only

Lists the internet exchanges (IXs) where NetActuate offers colocation, bare metal, virtual machines or remote peering, for example AMS-IX, DE-CIX and LINX. With no query it returns every exchange NetActuate publishes a page for; each result gives the slug, name, description, the opening paragraph of its page and its netactuate.com URL. Use it for peering and interconnection questions, such as 'does NetActuate peer at DE-CIX' or 'which exchanges offer remote peering'. Exchange pages name cities, not regions, so filter by city or exchange. A query also returns namedOnDataCenterPages: the data centers whose own pages name a matching exchange, with those lines, which covers exchanges without a page of their own (NL-IX at Amsterdam, JPNAP at Tokyo). For an exchange's full page use get_netactuate_page; for the data centers themselves, list_data_centers.

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_internet_exchanges"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWords that must all appear on the exchange's page: an exchange or city name, or a service, e.g. 'DE-CIX', 'Frankfurt', 'remote peering'.

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 / query / description
      Previous value: -"Filter by exchange or city name, e.g. 'DE-CIX' or 'London'."New value: +"Words that must all appear on the exchange's page: an exchange or city name, or a service, e.g. 'DE-CIX', 'Frankfurt', 'remote peering'."
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and closed-world, so the safety profile is covered. The description goes further by disclosing the result fields (slug, name, description, opening paragraph, URL) and a conditional extra field, namedOnDataCenterPages, that only appears with a query. It does not mention pagination or result caps for the unfiltered listing, which keeps it below a 5.

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 the core behavior, then result shape, then usage examples, then alternatives. Dense but almost every sentence carries guidance; the parenthetical '(IXs)' and repeated 'NetActuate' phrasing are minor slack.

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?

No output schema, no annotations gap, one optional parameter: the description covers scope, return fields, the query-triggered extra field, and the edge case of exchanges with no page (NL-IX, JPNAP). Nothing an agent needs in order to call it correctly is missing.

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%, so baseline is 3, but the description adds real meaning: the query is an AND of words matched on the exchange page, may be a city or a service, and the caveat that exchange pages name cities not regions steers how to filter. That is useful semantics beyond the schema text.

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?

States a specific verb and resource, enumerates what it covers (colocation, bare metal, VMs, remote peering) with concrete examples (AMS-IX, DE-CIX, LINX), and explicitly distinguishes itself from get_netactuate_page and list_data_centers. An agent can identify it without opening the 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?

Gives explicit use cases ('does NetActuate peer at DE-CIX', 'which exchanges offer remote peering'), states the no-query behavior, and routes to alternatives: get_netactuate_page for full pages and list_data_centers for the facilities themselves. When and when-not are both covered.

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