Skip to main content
Glama
Sign In

NetActuate

by com.netactuate
OverviewDiscussionsAdmin

Search NetActuate's published content

search_netactuate
Read-only

Keyword search across everything NetActuate publishes: the website (data centers, internet exchanges, products and pricing such as Media Substrate, MOQ Relay and the cost estimator, case studies, news, the facility FAQs), the marketplace's deployable apps, and the technical docs and API reference. Results come grouped by content type, ranked by relevance, as one-line summaries (a marketplace app and its setup page also carry its VM sizing, the app its free-demo terms); matchCounts gives the full count when a group is cut at limit. Results hold every word of the query (when none does, those holding the most, with a note), except a place: in 'Wowza Africa' the region, country or city is read as a location, the other words are searched, and place lists NetActuate's data centers there (the nearest ones for a city without a site). A query about VPUs also gets vpuLocations, where VPU capacity is live today (in the place, when one is named), and one naming a certification gets compliance, NetActuate's own certifications apart from its facilities'. Use it when no specific tool fits: product, pricing, software and how-to questions. For full text, pass a result's slug to get_netactuate_page, a listing's to get_marketplace_app, or a docs url to get_netactuate_doc.

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": {
      "query": "<query>"
    },
    "name": "search_netactuate"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results per content type, 1 to 50.
queryYesSearch terms, all of which must appear apart from a place (if none holds all, the most), e.g. 'renewable power', 'anycast DNS', 'live video', 'pricing', 'Wowza Africa'. Fewer, distinctive words find more.

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: -"Search terms, all of which must appear apart from a place, e.g. 'renewable power', 'anycast DNS', 'live video', 'pricing', 'Wowza Africa'. Fewer, distinctive words find more."New value: +"Search terms, all of which must appear apart from a place (if none holds all, the most), e.g. 'renewable power', 'anycast DNS', 'live video', 'pricing', 'Wowza Africa'. Fewer, distinctive words find more."
  4. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Search terms, all of which must appear, e.g. 'renewable power', 'anycast DNS', 'live video', 'pricing'. Fewer, distinctive words find more."New value: +"Search terms, all of which must appear apart from a place, e.g. 'renewable power', 'anycast DNS', 'live video', 'pricing', 'Wowza Africa'. Fewer, distinctive words find more."
  5. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results per content type."New value: +"Maximum results per content type, 1 to 50."
    • changedInput schema / properties / query / description
      Previous value: -"Search terms, e.g. 'renewable power', 'anycast DNS', 'live video', 'pricing'."New value: +"Search terms, all of which must appear, e.g. 'renewable power', 'anycast DNS', 'live video', 'pricing'. Fewer, distinctive words find more."
  6. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the read-only safety profile; the description adds substantial behavior beyond that: grouped-by-type, relevance-ranked output, one-line summaries, matchCounts when a group is truncated at `limit`, all-words-must-match with a documented OR fallback plus a note, and conditional extras (place, vpuLocations, compliance). That is exactly the kind of return-shape and edge-case disclosure annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded correctly — purpose first, caveats and routing after — and nearly every clause carries information. But the body is one sprawling semicolon-and-parenthesis chain that an agent must parse linearly, and the parenthetical asides (Media Substrate, MOQ Relay, VM sizing) could be trimmed without losing selectable meaning.

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 exists, so the description must carry the return contract, and it does: grouping, ranking, summary format, matchCounts semantics, and the conditional place/vpuLocations/compliance fields. Combined with explicit hand-off instructions for full text, an agent has everything needed to call it and use the result.

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 both parameters are already documented; the description nonetheless adds real semantics: the place exception to all-words matching ('Wowza Africa'), how `limit` interacts with matchCounts, and the 'fewer, distinctive words find more' heuristic. It stops short of adding anything about `limit`'s per-content-type scope beyond what the schema says, so not a full 5.

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 ('Keyword search across everything NetActuate publishes') and enumerates the covered corpora: website sections, marketplace apps, technical docs and API reference. An agent can tell what this tool returns without opening the schema, and the closing line separates it from the topical siblings.

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?

Explicitly gives the selection rule — 'Use it when no specific tool fits: product, pricing, software and how-to questions' — and then routes the agent onward: slugs to get_netactuate_page, listing slugs to get_marketplace_app, docs urls to get_netactuate_doc. When-to-use, when-to-delegate and the follow-up path are all named.

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