Skip to main content
Glama

tm_verify_domain_http

DestructiveIdempotent

Verify domain ownership via HTTP: fetch a verification token from the domain's .well-known URL and match it to confirm the domain. Alternative to DNS verification for users who can serve a static file.

Instructions

Run the HTTP-token verification check on a previously-added domain.

The server fetches https://<domain>/.well-known/trafficmorph-verify.txt (falling back to plain HTTP if HTTPS fails) and matches the file body against the verificationToken issued by :func:tm_add_domainthe same token DNS verification uses; there's only one token per domain. On match, the domain flips to verified=true.

Alternative to :func:tm_verify_domain_dns for users who can serve a static file at the target host but can't edit DNS.

Same fail-fast contract: misses return 400 with the expected URL + token in the message, not a "still pending" 200. The error message is constructed to be readable directly to the user (no JSON parsing required by the AI host).

Success response: VerifiedDomainResponse with verified=true, verifiedAt populated, and verificationMethod="HTTP" (uppercase — matches the server's stored value, see :func:tm_verify_domain_dns for the full set of method tokens).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domain_idYes
Behavior5/5

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

Provides detailed behavioral information: fetches file from .well-known, fallback to HTTP, matches token, flips verified, error response format, success response shape. Adds value beyond annotations.

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?

Well-structured with clear paragraphs. Each sentence provides necessary information without redundancy. Front-loaded with the main action.

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?

Covers purpose, process, alternatives, error handling, and response format. Despite no output schema, description makes usage clear. Sufficient for a verification tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though schema coverage is 0% and only one parameter (domain_id), the description adds context on how the parameter is used in the verification process. Minimal but sufficient.

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?

Clearly states the tool verifies a domain via HTTP token check. Distinguishes from sibling tm_verify_domain_dns by explicit alternative.

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?

Describes when to use this tool as alternative to DNS verification for users who can serve a static file. Does not provide explicit exclusions but gives clear context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/trafficmorph-gif/tm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server