Mixer4AI

Check Self-Registration Domain Challenge

check_self_registration_domain_challenge

Idempotent

Answers the domain-binding challenge: makes one outbound, Server-Side Request Forgery (SSRF)-guarded, per-host rate-limited HTTPS GET to the well-known path this draft's status already names (domainChallengeWellKnownPath) on the declared URL's host, and checks it serves back the exact domainChallengeToken. Serve that token at that path on your domain BEFORE calling this. Repeat calls re-run the same probe and simply re-record its current result. Requires the access code.

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": {
      "id": "<id>",
      "accessCode": "<accessCode>"
    },
    "name": "check_self_registration_domain_challenge"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The draft's id, as returned by self_register_agent_card.
`accessCode`	Yes	The one-time access code returned by self_register_agent_card for this draft.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

addedInput schema / properties / accessCode / description

Added value: +"The one-time access code returned by self_register_agent_card for this draft."

addedInput schema / properties / id / description

Added value: +"The draft's id, as returned by self_register_agent_card."

First observedJul 27, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial behavioral detail beyond annotations: SSRF guarding, per-host rate limiting, exact outbound method and path, access-code requirement, and that repeat calls re-run and re-record the probe result. This clarifies the non-read-only nature and the idempotent-but-side-effecting behavior.

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

Conciseness5/5

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

Three sentences, front-loaded with the core action, then prerequisites, repeat behavior, and access requirements. Dense but every sentence carries useful operational information.

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?

Covers the operation, prerequisites, and repeat behavior well. Since there is no output schema, it could say more about the shape of the recorded result, but the essential calling information is 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 coverage is 100%, so both parameters are already documented. The description reinforces that the access code is required and that the id comes from self_register_agent_card, but adds little syntactic or semantic detail beyond the schema.

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 operation: answering a domain-binding challenge by making an outbound HTTPS GET to a well-known path and checking for the exact token. The domain-specific scope distinguishes it from the endpoint challenge sibling, even though that sibling is not named.

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?

Gives a clear prerequisite (serve the token before calling) and explains repeat-call behavior. It does not explicitly say when to choose this over check_self_registration_endpoint_challenge, so it falls short of full when/when-not guidance.

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

All Mixer4AI 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?