Skip to main content
Glama

Cycle MCP

by io.cycle.mcp.na
OverviewDiscussionsAdmin

Check DNS Resolution and Propagation

check_dns_propagation
Read-onlyIdempotent

Answer "why doesn't this domain work yet" by asking DNS directly, from two sides at once: the zone's OWN authoritative nameservers (read from its live NS delegation, so whatever actually answers — one of Cycle's na/eu pools, or an outside provider) and the public recursive resolvers (what a real client sees). Comparing the two separates failures that look identical from a browser: resolved, propagating (nameservers have it, public resolvers not yet — WAIT for the TTL, change nothing), no-address (name exists, no A/AAAA — on Cycle, a LINKED record whose target has not published addresses), nxdomain (never created or deleted), or unknown (nothing reachable — proves nothing either way). The verdict's detail explains each case in context.

It also reports whether Cycle itself holds a record for this name (zone, type, and for LINKED records the container/VM/deployment it targets), which distinguishes "never created in Cycle" from "exists and still spreading".

Pass wait_seconds to keep re-probing until the name resolves everywhere. Read-only: only asks questions of DNS servers. To create or repoint a record, use manage_dns_record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesFully qualified domain name to probe, e.g. 'app.example.com'. Pass the hostname a user would actually visit, not the zone.
contextNoWhy are you calling this tool? Briefly describe the user's goal.
record_typesNoRecord types to query. Defaults to a and aaaa, which is what matters for reaching a container or VM.
wait_secondsNoKeep re-probing until the name resolves consistently, up to this many seconds. 0 (default) returns a single snapshot. Propagation usually outlasts any single call — a 'propagating' verdict after the wait is not a failure, just call again.
conversation_idNoConversation tracking id. Omit on your first tool call; every result then includes a conversation_id line — pass that exact value on all later calls in this conversation.
nameserver_groupNoForce which Cycle nameserver pool is treated as authoritative ('all' queries every pool). Omit to follow the zone's own delegation, which is what actually answers for it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/open-world, so the bar is lower, yet the description adds substantial context: a full verdict taxonomy (resolved, propagating, no-address, nxdomain, unknown), the meaning of each, the caveat that 'unknown' proves nothing, and that it reports whether Cycle holds a record (zone/type/target for LINKED). This goes well beyond what annotations provide.

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?

Purpose and the two-sided mechanism are front-loaded, and sentences are information-dense. It is long for a single tool, with minor redundancy (the read-only claim restates readOnlyHint), but nearly every sentence carries semantic weight, so it stays structured rather than bloated.

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 carries the burden of explaining returns, and it does so via the verdict taxonomy and the Cycle-record distinction. An agent has enough to call it correctly and interpret results, including the propagation-over-time caveat.

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 meaning: it explains what passing wait_seconds does ('keep re-probing until the name resolves everywhere') and how to interpret a propagating verdict after a wait ('not a failure, just call again'). It does less for the record_types/nameserver_group nuance, which stays in the schema, keeping this at 4 rather than 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?

Names a specific action (check DNS resolution/propagation) and a specific resource (DNS), and immediately frames it with an observable verb+scope: 'asking DNS directly, from two sides at once.' It clearly distinguishes itself from manage_dns_record and delete_dns_record by scoping to read-only diagnosis.

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?

States the exact triggering situation ('why doesn't this domain work yet'), enumerates the verdicts that guide follow-up action (propagating -> WAIT, change nothing), and explicitly names the alternative for mutations: 'To create or repoint a record, use manage_dns_record.' When/when-not and the alternative are both present.

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

All Cycle MCP 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