Skip to main content
Glama

Cnamio

Check propagation now

recheck_propagation
Idempotent

Asks Cnamio to check the domain's authoritative nameservers again now (at most once every 5 minutes per connection).

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": {
      "jobId": "<jobId>"
    },
    "name": "recheck_propagation"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesjob_id returned by connect_domain or connect_domain_automatic

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new context in the per-connection rate limit, but omits what happens when the limit is exceeded and whether the call blocks, returns immediately, or is asynchronous.

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?

One sentence, no filler, with the action front-loaded and the rate limit parenthetically appended. It is efficiently sized, though the terseness leaves no room for the routing or return-value guidance an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description does not say what the call yields — a fresh status, a queued acknowledgement, or nothing to poll later via get_connection_status. For a state-changing trigger with an external side effect (openWorldHint=true), that is a meaningful omission, though the rate limit and required job id cover the essentials for invocation.

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 coverage is 100% and the single jobId parameter is documented in the schema with its pattern and provenance (connect_domain or connect_domain_automatic). The description adds nothing about the parameter, which is acceptable at full coverage but leaves no value-add.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('check ... again now') and a specific resource ('the domain's authoritative nameservers'), with the 'again' signalling a re-trigger rather than a first lookup. It does not explicitly contrast itself with check_domain or get_connection_status, so an agent must infer that this is the force-refresh variant.

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

Usage Guidelines3/5

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

Usage is implied (re-verify propagation after a connect) and the description supplies a hard constraint of at most once per 5 minutes per connection, which usefully bounds when it can be called. However, it never states the condition that selects this tool over check_domain or get_connection_status, nor what to do while waiting for results.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources