Skip to main content
Glama
Sign In

NetActuate

by com.netactuate
OverviewDiscussionsAdmin

Get one NetActuate page in full

get_netactuate_page
Read-only

Returns the full published text of one NetActuate page other than a data center: a product, solution, product category, case study, region, internet exchange or company page. Gives its summary, section headings, body copy and FAQs, with its netactuate.com URL. Use it when a question needs more than search_netactuate's one-line summaries: how Media Substrate works, what the pricing page says, what a case study found. Accepts a slug or URL from search_netactuate or list_services, or a page name such as 'Media Substrate' or 'MOQ Relay'. A name matching several pages returns up to ten candidates with their slugs rather than a guess. A very long page is cut to fit, with a note saying how much is shown; the whole page is at its URL. For a data center use get_data_center.

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": {
      "page": "<page>"
    },
    "name": "get_netactuate_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesA slug or URL from search_netactuate or list_services (e.g. 'media-substrate', 'solutions/dns-services', 'https://netactuate.com/pricing'), or a page name (e.g. 'Media Substrate').

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. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the read-only annotations, it discloses the return payload (summary, section headings, body copy, FAQs, canonical URL), the truncation behavior for long pages plus the note explaining how much is shown, and the ambiguity policy of returning up to ten candidate slugs instead of guessing. These are behaviors an agent could not infer from structured fields.

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 return content and followed by the routing rule, the input forms, and the two edge-case behaviors — every sentence carries information. The page-type enumeration is somewhat long but is functional for scope checking.

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?

Single-parameter read tool with no output schema, and the description covers return contents, truncation, disambiguation, alternate routing, and accepted input forms. Nothing an agent needs 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 the schema already documents the accepted slug/URL/name forms; the description restates them but adds the important semantic that a name matching several pages yields a candidate list. It does not add format or normalization rules beyond that, so it slightly exceeds the baseline of 3.

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 ('Returns the full published text of one NetActuate page') and enumerates the covered page types (product, solution, category, case study, region, internet exchange, company). It also explicitly excludes data centers, which separates it cleanly from get_data_center and search_netactuate.

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 an explicit trigger ('when a question needs more than search_netactuate's one-line summaries') with three concrete examples of such questions, and routes the data-center case to get_data_center. Both the use case and the alternative are 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