Skip to main content
Glama

request_domain_verification

Optional: prove control of a domain. Not required for anything — use agent_key instead.

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": {
      "hostname": "<hostname>"
    },
    "name": "request_domain_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostnameYesYour domain, e.g. "acme.com".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / hostname / description
      Added value: +"Your domain, e.g. \"acme.com\"."
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already cover the safety profile (non-read-only, open-world, non-idempotent, non-destructive), and the description adds the useful point that skipping this path is acceptable. However, it says nothing about what a call produces or what the follow-up step is, so an agent has no picture of the flow beyond 'optional'.

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?

Two short sentences, front-loading the optional framing with no filler. It is efficient, though the phrasing 'prove control' is slightly vague for a front-loaded statement of purpose.

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?

For a one-parameter tool this is close to sufficient, and having no output schema lowers the bar. Still missing is any mention of the next step (presumably verify_domain) or what the caller must do with the result, which is essential to using a verification flow correctly.

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%, with the single hostname parameter fully documented in the schema including an example. The description adds no meaning beyond that, which is the expected baseline for a one-parameter tool.

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

Purpose3/5

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

The description says 'prove control of a domain,' which gives a rough sense of the tool's aim, but it never clarifies what 'request' actually does (e.g. issue a challenge, return a DNS token) or how it differs from the sibling verify_domain. An agent cannot tell from this text whether it is starting a verification flow or completing one.

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?

Explicitly frames the tool as optional and names the alternative ('use agent_key instead'), which is strong negative guidance. It falls short of saying when a caller would actually want it, such as to earn a verified badge, so the positive use case is left implicit.

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