Skip to main content
Glama
Sign In

InfraNest

by io.infranest
OverviewDiscussionsAdmin

DNS changes made outside InfraNest

dns_outside_changes
Read-onlyIdempotent

Records changed at the DNS provider outside InfraNest that nobody has decided on yet, newest first, each with what the record was and is now. writable says whether your earlier value can be put back for this zone. Use it for "did anyone change my DNS outside InfraNest": edits made directly at the DNS provider that nobody has kept or undone yet, each with the value before and now. writable says whether the earlier value can be put back. This connector cannot change records; to keep or undo a change, open the zone in InfraNest (its app_url). For the whole history from every source use dns_zone_changes.

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": {
      "zone_id": "<zone_id>"
    },
    "name": "dns_outside_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
zone_idYesThe zone id, from list_dns_zones or the number of a search hit zone:N.
organization_idNoThe organization to read. Leave it out when the token reaches only one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / zone_id / description
      Previous value: -"The zone id, from list_dns_zones."New value: +"The zone id, from list_dns_zones or the number of a search hit zone:N."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds real value on top: the result is filtered to undecided changes only, returned newest-first with before/now values, and each row carries a `writable` flag indicating whether the prior value can be restored. It also states the remediation path lives in the InfraNest app, not in this tool.

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

Conciseness2/5

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

The description is nearly duplicated end to end: the scope definition and the `writable` explanation each appear twice in slightly reworded form ("`writable` says whether your earlier value can be put back for this zone" / "`writable` says whether the earlier value can be put back"). The core facts are front-loaded, but a roughly 40% redundant payload wastes attention on a tool whose schema already explains its two parameters.

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?

For a two-parameter read tool with no output schema, annotations covering safety, and full schema coverage, nothing needed to call it correctly is missing: scope, ordering, per-record contents, the `writable` indicator, the no-mutation constraint, the remediation path, and the alternative tool are all present.

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%, with zone_id's origin (list_dns_zones or a search hit's zone:N) and organization_id's optionality already documented in the schema. The description adds no parameter-level guidance such as what happens when organization_id is set to a different org than the zone. Baseline 3 applies since the schema carries the burden.

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 resource (DNS records changed directly at the provider, outside InfraNest) with a precise scope filter (only changes nobody has kept or undone yet) and ordering (newest first, each with before/after values). It explicitly contrasts itself with the sibling dns_zone_changes, so an agent can pick between the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It supplies a concrete user-intent trigger ("did anyone change my DNS outside InfraNest") and names the alternative tool dns_zone_changes for the full cross-source history. It also warns that this connector cannot mutate records and points to the InfraNest app_url for remediation, which is clear routing. It stops short of explicit exclusions beyond those two, so it is strong rather than exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All InfraNest 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