Skip to main content
Glama

Paragon Boxing & BJJ Gear Advisor

verify_merchant_identity

Read-onlyIdempotent

Limited did:web and Ed25519 eddsa-jcs-2022 verifier for public DNS domains. Fetches same-domain DID and credential with public-address DNS screening, no redirects, size/time limits and strict proof checks. Validates one standalone proof, not proof chains, revocation or commercial truth. No OAuth, carts, customer data or payment access. Unsupported documents are reported, not guessed valid.

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": {
      "domain": "<domain>"
    },
    "name": "verify_merchant_identity"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesBare public ASCII DNS domain, without scheme or port.
credential_urlNoOptional HTTPS same-domain URL under /.well-known/, without query, fragment, port or credentials.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, and the description still adds substantial behavioral context beyond them: same-domain fetch only, public-address DNS screening, no redirects, size and time limits, strict proof checks, and the fail-closed policy of reporting unsupported documents instead of guessing them valid. That is exactly the kind of operational detail annotations cannot express.

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?

Five tight sentences, front-loaded with the core capability before limitations, with no filler. The telegraphic style ('No OAuth, carts, customer data or payment access') is efficient though slightly list-like rather than prose.

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?

For a two-parameter, annotation-covered, read-only verification tool this covers scope, constraints, and failure policy well. The one gap is that with no output schema, the description never says what a result looks like beyond 'unsupported documents are reported' — an agent knows the verdict exists but not its shape.

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?

Schema coverage is 100%, so both parameters are already documented, but the description still contributes meaning: 'public DNS domains' and 'public-address DNS screening' clarify that the domain must resolve publicly, and 'same-domain' reinforces the credential_url constraint. The added value over the schema is real but modest.

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?

The first two sentences name a specific verb (verify), the exact credential technology (did:web, Ed25519 eddsa-jcs-2022), and the scope (public DNS domains, same-domain DID and credential). An agent can tell exactly what this does and, via the 'not proof chains, revocation or commercial truth' clause, what it does not.

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?

The description sets clear boundaries: one standalone proof only, no proof chains, no revocation checks, no OAuth/carts/customer data/payment access. That effectively tells an agent when the tool is inappropriate. It does not name an alternative tool for those excluded cases, which keeps it short of a 5, but the sibling list contains no overlapping verifier to route to.

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