Skip to main content
Glama

Check the proof that my sites are mine

verify_job_sites
Idempotent

A website test starts only when each of its sites is proved yours: publish the job's verification.token (get_job) for every site as a file at https:///.well-known/agentmart-verify.txt, a DNS TXT record agentmart-verify=, or on the start page, then call this with the job_id (status needs_verification). Every site proved: the job is queued, or joins our queue by itself once it has room, and its promise starts then. Otherwise the error says what each site lacks; proved sites stay proved.

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": {
      "job_id": "job_exampleexampleexample2"
    },
    "name": "verify_job_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob id (job_...) from buy (delivery.job_id) or list_jobs.
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: +[
      +  {
      +    "job_id": "job_exampleexampleexample2"
      +  }
      +]
    • 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. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations say readOnlyHint=false, idempotentHint=true and openWorldHint=true, and the description supplies the behavior behind those flags: a successful call queues the job or defers it until the queue has room, and the promise starts only then. Crucially it discloses that partial progress persists ('proved sites stay proved'), which is exactly the non-obvious state an agent needs to retry safely.

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?

It is one dense paragraph with no filler: the token-publishing instructions, the call condition, the outcome, and the error semantics all earn their place. The weakness is front-loading — it opens with the prerequisite rather than stating what the tool does, and the three publication methods make it a heavy read.

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?

There is no output schema, and the description compensates by explaining both success outcomes (queued now, or queued when room appears) and failure shape (per-site missing-proof errors). Combined with the persisted-verification note, an agent has everything needed to call and interpret this tool.

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 job_id (including its provenance from buy/list_jobs) and passport_token are already documented in the schema. The description adds only a small amount of meaning, tying job_id to the needs_verification state, and never mentions the passport_token fallback path. Baseline 3 is appropriate when the schema already carries the parameter documentation.

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

Purpose4/5

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

The description makes clear that this tool checks ownership proofs for every site in a job and thereby releases the job into the queue. It even points to the sibling get_job as the source of the verification token. It stops short of a crisp verb-first summary (the actual action is buried in 'then call this with the job_id') and does not differentiate from a similarly named sibling such as check_site.

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?

It states the precondition exactly: the job must be in status needs_verification, and the token must already be published in one of three enumerated forms, each with a concrete location. It also states what to expect when the precondition is unmet ('the error says what each site lacks'), so an agent knows the retry loop.

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.