Skip to main content
Glama

Check a tracking domain now

verify_tracking_domain
Destructive

Use this right after the user added the CNAME record of their tracking domain, to check it now instead of waiting for the next check, which runs every 5 minutes on its own. Returns the domain as the check leaves it: pending_dns or verifying while it is not live yet, active once it is. A failed domain gets another day of checks. Checks are limited to 200 a day, so never call this in a loop to follow a domain. Free.

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": {
      "trackingDomainId": "<trackingDomainId>"
    },
    "name": "verify_tracking_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackingDomainIdYesThe tracking domain's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the 200/day quota, the cost ('Free'), the retry behavior for failed domains ('another day of checks'), and the possible resulting states. The one gap is that destructiveHint=true is never reconciled with the description's framing of this as a check — an agent gets no hint about what side effects the trigger has beyond quota consumption.

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-loads the trigger condition, then the return states, then the quota warning — a sensible order with no filler. The middle sentence about return states is slightly dense but every clause carries information.

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 correctly takes on the burden of explaining return values (pending_dns, verifying, active) and adds the operational constraints an agent needs. For a one-parameter trigger tool, nothing material is missing.

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 parameter is fully documented in the schema, so the description adds no meaning beyond it. Baseline 3 applies; the description neither names the parameter nor explains how to obtain the id.

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 ('check' the 'tracking domain') and pins the exact moment it applies: right after the CNAME record is added. It is clearly distinguishable from create_tracking_domain, delete_tracking_domain, and list_tracking_domains without opening any schema.

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 explicit when-to-use ('right after the user added the CNAME record'), the alternative it replaces (waiting for the automatic 5-minute check), and an explicit when-not ('never call this in a loop to follow a domain'). Nothing about invocation timing is left to inference.

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