Skip to main content
Glama
Sign In

NetActuate

by com.netactuate
OverviewDiscussionsAdmin

Find the nearest NetActuate PoPs

find_nearest_data_centers
Read-only

Ranks NetActuate data centers by great-circle distance from a place named in the question: the market to be served, where the end users are, or a city being compared. Use for 'what is your closest location to Lagos', 'which sites would serve users in Japan' or latency planning. Pass the place the question is about, not where the person asking is, unless they ask for the site nearest them and say where that is. Each result is a site summary with distanceKm, nearest first. Distances are computed from city centroids, so treat them as approximate guidance, not a latency guarantee. Places are matched against a built-in list of major cities and countries; one it does not know is reported, and latitude and longitude can be passed instead.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many sites to return, 1 to 20.
latitudeNoLatitude in decimal degrees, with longitude, when the place name is not recognised.
locationNoThe place to measure from: the target market or the end users' city or country, e.g. 'Lagos', 'Berlin', 'Osaka, Japan'. Omit if passing coordinates.
longitudeNoLongitude in decimal degrees, with latitude, when the place name is not recognised.

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. Changed3 schema fields changed
    • changedInput schema / properties / latitude / description
      Previous value: -"Latitude, if the place name is not recognised."New value: +"Latitude in decimal degrees, with longitude, when the place name is not recognised."
    • changedInput schema / properties / limit / description
      Previous value: -"How many sites to return."New value: +"How many sites to return, 1 to 20."
    • changedInput schema / properties / longitude / description
      Previous value: -"Longitude, if the place name is not recognised."New value: +"Longitude in decimal degrees, with latitude, when the place name is not recognised."
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld=false, so safety is covered; the description goes further by disclosing that distances are computed from city centroids and are approximate guidance, not a latency guarantee, and that unrecognized places are reported back with a coordinate fallback. It also describes the result shape and ordering (site summaries with distanceKm, nearest first).

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?

Front-loads the core action and scope, then layers examples, the asker-vs-target rule, and the centroid caveat in descending order of importance. Every sentence carries information an agent needs to call this correctly; none is filler or restatement of the title.

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 still discloses the return shape (site summaries with distanceKm, nearest first) and the failure mode for unknown places. For a four-parameter, zero-required lookup tool, nothing an agent needs in order to invoke 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 the baseline is 3; the description earns above that by adding genuine semantic direction for `location` (the target market or end-user city, not the asker's own location) and by explaining the latitude/longitude pair as the fallback path when a place name is unrecognized. It adds no detail on `limit` beyond the schema, but that parameter is self-explanatory.

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 (ranks) and resource (NetActuate data centers) plus the ranking criterion (great-circle distance from a named place). This clearly separates it from the sibling list_data_centers, which lists without ranking, and the location-based framing is unambiguous.

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 concrete example phrasings ('what is your closest location to Lagos', 'which sites would serve users in Japan') and states the key when-not rule: pass the place the question is about, not where the asker is, unless they explicitly ask for the site nearest them. That is an explicit disambiguation of a common agent error rather than an implied one.

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