Democruit

Check website address

check_website_domain

Read-onlyIdempotent

Read the DNS status of a connected website domain. Poll every 15 seconds for up to 10 minutes. Use manage_website_domain operation=refresh to re-check DNS. Operations: status. Returns the response envelope; nextActions list what the user can do next, primary first.

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": {
      "operation": "<operation>"
    },
    "name": "check_website_domain"
  }
}

Input Schema

Name	Required	Description
`cursor`	No	Optional. Omit to use the default first page; do not ask the user unless they request this setting.
`detail`	No	Optional. Omit to use the default compact response; do not ask the user unless they request this setting.
`operation`	Yes	Choose the task. Each operation accepts only its own fields.
`pollStartedAt`	No	Use the server-provided polling window timestamp from the previous next action.
`personalWebsiteId`	No	Optional when exactly one candidate item exists: omit its ID to use that item. Ask which saved item to use only when several exist.

Output Schema

Name	Required	Description	Default
`data`	No
`page`	No
`error`	No
`links`	No
`status`	Yes
`notices`	No
`polling`	No
`summary`	Yes
`agentHint`	No
`nextActions`	Yes
`appliedDefaults`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), but the description adds real behavioral context: the 15-second poll interval, the 10-minute maximum window, and the ordering of nextActions (primary first). It doesn't explain what happens if polling expires, but the timing and response-shape details are meaningful additions beyond the annotations.

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?

The most important information (what it reads, polling behavior, alternative) is front-loaded in the first three sentences, and there is little filler. 'Operations: status.' is close to redundant with the single-value enum in the schema, but the overall size is appropriate.

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

Completeness4/5

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

Given that an output schema exists and annotations cover the safety profile, the description is nearly complete: purpose, polling behavior, alternative, and nextActions ordering are all present. The only gap is what to do when the 10-minute polling window ends without a definitive result.

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% and the schema already explains cursor, detail, operation, pollStartedAt, and personalWebsiteId, so the schema carries the parameter burden. The description only indirectly gestures at pollStartedAt through the polling window sentence and adds no syntax or format detail beyond that, which is the expected baseline.

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 opens with a specific verb and resource: 'Read the DNS status of a connected website domain.' It also names the distinct sibling operation for re-checking DNS (manage_website_domain operation=refresh), so an agent can separate this read-only status check from the management tool 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 states the situation for use (checking a connected domain's DNS status), names the alternative for a re-check, and gives the polling cadence and 10-minute ceiling so the agent knows how long to wait. It does not state an explicit when-not-to-use condition, which keeps it short of a 5.

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

All Democruit tools Inspect

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

Need Help?