Skip to main content
Glama

Prove a domain for a site check badge

prove_domain
Idempotent

Step 1 of a site check badge. The first call gives a TXT record to publish on _agentmart-check.; publish it, then call again with the same domain: status proved, waiting_for_proof (with the problems) or lost. Once proved and your human says yes to $5 for 30 days, buy_site_badge within 7 days. Free; 20 looks per domain an hour.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "example.com"
    },
    "name": "prove_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesYour owner's domain, like example.com.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "domain": "example.com"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true), and the description goes well beyond them: it enumerates the three possible outcomes (proved, waiting_for_proof with the problems, lost), discloses that it is free, and states the rate limit of 20 looks per domain per hour. Nothing contradicts 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?

Front-loaded with the step identity, then the operational sequence, then cost and limits; nearly every clause earns its place. The second sentence is dense and chains several ideas with semicolons and commas, which slightly reduces scannability but doesn't waste words.

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?

This is a stateful two-call tool with no output schema, and the description covers all of it: the first-call artifact, the verification outcomes, the human-approval gate, the downstream purchase window, and the rate limit. An agent has enough to drive the whole 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 description coverage is 100%, so both domain and passport_token are already documented in the schema, and the baseline is 3. The description adds mild value by showing how domain is used to construct the _agentmart-check.<domain> record and by stressing that the same domain must be passed on the follow-up call, but it says nothing about the passport_token fallback.

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 ('Prove a domain') and frames it as 'Step 1 of a site check badge', which cleanly separates it from the sibling buy_site_badge that is the later step. An agent can identify both the action and its place in the pipeline 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 an explicit protocol: call once to receive a TXT record for _agentmart-check.<domain>, publish it, then call again with the same domain. It also states the precondition for the next step (human must approve $5 for 30 days) and the deadline (buy_site_badge within 7 days), so when-to-use and when-to-advance are both spelled out.

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.