Skip to main content
Glama

audit.domains - Domain Valuation

by domains.audit
OverviewDiscussionsAdmin

Verify an audit.domains certificate

verify_certificate
Read-onlyIdempotent

Check an audit.domains certificate from its verifier URL or serial with two separate checks. Integrity recomputes the SHA-256 digest of the printed fields and needs the full URL; it proves the fields were not altered, not who made them. Issuer authenticity makes one request to the issuer's public verify endpoint to see whether a signed record for the serial reproduces. verified is true only when every check that could run passed; a record that names no signer is not verified. Failures carry a reason code such as integrity_mismatch or not_issued. Runs no valuation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoVerifier URL printed on the certificate, https://audit.domains/verify/<serial>?p=<token>. Runs both the integrity and issuer checks.
serialNoCertificate serial alone. Runs the issuer check only.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputNo
notesNo
citeAsYesA structured citation. Quote `text` or build your own from the fields. Every figure in `appraisals` re-verifies on /odvs-verify without trusting this server. Tools whose answer is not an appraisal (a bracket, which withholds estimates by contract, and the recorded-sales tools, whose rows are not hashed) return an empty `appraisals`. A stored interval also has no ODVS record: its artifact digest is provenance, not a standalone proof of these projected fields.
issuerYesstatus is authentic, not_issued, unsigned_legacy_certificate, unverified_no_key_named, signature_mismatch, issuer_key_unavailable, unreachable or bad_response. Carries the endpoint queried, httpStatus, signingKeyId and the raw response.
citationYes
verifiedYesTrue only when every check that could run passed and none failed.
integrityYesstatus is match, mismatch or not_checked. When checked: canonicalString, carriedDigest, recomputedDigest, fields.
retryableNoTrue when repeating the call later may change the outcome.
semanticsNo
consistencyNoThe link's domain, serial, value and date against the issuer's signed record. status is match, mismatch or not_checked.
reasonCodesYesEmpty when verified.
schemaVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / citeAs / description
      Previous value: -"A structured citation. Quote `text` or build your own from the fields. Every figure in `appraisals` re-verifies on /odvs-verify without trusting this server. Tools whose answer is not an appraisal (a bracket, which withholds estimates by contract, and the recorded-sales tools, whose rows are not hashed) return an empty `appraisals`."New value: +"A structured citation. Quote `text` or build your own from the fields. Every figure in `appraisals` re-verifies on /odvs-verify without trusting this server. Tools whose answer is not an appraisal (a bracket, which withholds estimates by contract, and the recorded-sales tools, whose rows are not hashed) return an empty `appraisals`. A stored interval also has no ODVS record: its artifact digest is provenance, not a standalone proof of these projected fields."
  2. Added
  3. Removed
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds real behavioral context beyond that: it makes one network request to the issuer's public endpoint, defines the verified semantics (true only if every runnable check passed, no-signer means not verified), and enumerates failure reason codes.

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 core action and the two checks, then the verified semantics and reason codes. Dense but every sentence carries information; the closing 'Runs no valuation' earns its place as a disambiguator against appraisal siblings, though the passage is slightly long.

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?

An output schema exists, so return values need not be explained. The description still covers the semantics an agent needs to interpret results (verified flag behavior, no-signer case, reason codes) and the two input modes, leaving no meaningful gap.

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 the schema already documents both url and serial, including the exact URL format and that serial runs issuer-only. The description reinforces that integrity needs the full URL but adds no syntax or meaning beyond what the schema provides, so baseline 3 applies.

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 (verify/check) and resource (audit.domains certificate) and decomposes it into the two concrete checks it performs. It also distinguishes itself from sibling tools by noting 'Runs no valuation', which separates it from appraise_domain and the appraisal/purchase siblings.

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?

Clearly explains the two invocation modes: a full verifier URL runs both the integrity and issuer checks, while a serial alone runs only the issuer check. It doesn't name a sibling alternative or an explicit when-not-to-use, but the mode-selection guidance is clear and directly actionable.

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

All audit.domains - Domain Valuation toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources