Skip to main content
Glama

Domain portfolio audit — Atom

Domain portfolio audit

domain_portfolio_audit
Read-onlyIdempotent

Submits a domain-portfolio manifest (inventory, brand architecture, declared domain rows, DNS, redirects, email authentication, TLS, renewals, audit) and returns a deterministic DOMAIN_PORTFOLIO_SOUND / DOMAIN_PORTFOLIO_NOT_SOUND / INSUFFICIENT_EVIDENCE verdict across four sections, including computed canonical-per-cluster, redirect-graph, email-auth coverage and renewal checks, with per-check evidence. Audits the declared portfolio; it performs no live DNS lookups.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "domain_portfolio_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
dnsNoDNS evidence.
tlsNoTLS evidence.
auditNoAudit-cadence evidence.
domainsNoDeclared domains: {name, registrar, renewal_date, status, purpose, owner, brand_cluster, is_canonical, is_personal_brand, redirect_target, redirect_status_code, sends_email, spf_declared, dkim_declared, dmarc_declared, spoofing_blocked, registrar_lock, auto_renew}.
renewalsNoRenewal evidence.
inventoryNoInventory evidence.
portfolioNoPortfolio being audited.
redirectsNoRedirect-posture evidence.
email_authNoEmail-authentication evidence.
evaluation_dateNoEvaluation date (ISO) renewal checks are computed against.
brand_architectureNoBrand-architecture evidence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the result is deterministic, computed checks span canonical-per-cluster, redirect graph, email-auth coverage and renewals, and evidence is returned per check. It does not explain what triggers INSUFFICIENT_EVIDENCE or whether the audit ever errors rather than returning that verdict, which keeps it below a 5.

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?

Two sentences, front-loaded with the action, and the scope caveat is placed last for emphasis without padding. The nine-item parenthetical inventory list (inventory, brand architecture, DNS, redirects, email authentication, TLS, renewals, audit) largely echoes the schema property names and could be trimmed, but it is not wasteful enough to hurt overall.

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?

With 11 parameters, nested objects and no output schema, the description carries the burden of explaining returns — and it does, naming the three verdicts, the four sections, and per-check evidence. The main residual gap is the lack of guidance on how much of the manifest must be populated for a sound verdict versus INSUFFICIENT_EVIDENCE, and that detail lives only in an external SERVICE.md reference.

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 the baseline would be 3; the description earns above that by mapping manifest sections to the specific computations they feed (canonical-per-cluster, redirect-graph, email-auth coverage, renewal checks), telling the agent which inputs actually drive which verdicts. It still defers row-level detail to the referenced SERVICE.md and does not explain the expected shape of evidence sub-objects.

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 ('submits a domain-portfolio manifest') plus the exact output contract: three named verdicts (DOMAIN_PORTFOLIO_SOUND / NOT_SOUND / INSUFFICIENT_EVIDENCE) across four sections. The second sentence narrows the scope ('audits the declared portfolio; no live DNS lookups'), so an agent knows precisely what class of operation this is. No siblings exist to disambiguate against, but the purpose itself is unambiguous.

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 closing clause 'it performs no live DNS lookups' effectively states when to use this (auditing declared/evidence-stage data) versus when not to (live verification), which is the key routing decision for this tool. What is missing is any statement of prerequisites — e.g. whether a minimal manifest can be submitted or which sections are needed to avoid INSUFFICIENT_EVIDENCE.

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.