Skip to main content
Glama

BRAINIAC Domain Security

Audit custom domain onboarding

domain-security_custom-domain-onboarding-audit

Compare a custom domain, tenant, ownership TXT records, DNS targets, and platform assignment status. A dangling name is a potential condition only when the supplied assignment is unassigned or deleted. The audit does not query DNS or claim the domain. Price $0.05 USDC. POST /api/v1/domain-security/custom-domain-onboarding-audit. Unpaid calls return 402 and do not run.

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>",
      "tenant": "<tenant>",
      "verification": "<verification>",
      "records": "<records>",
      "token": "<token>",
      "targets": "<targets>"
    },
    "name": "domain-security_custom-domain-onboarding-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
domainYes
statusNo
tenantYes
recordsYes
targetsYes
previousNo
checkedAtNo
assignmentsNo
certificatesNo
verificationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does add real behavioral context: it does not perform DNS lookups or claim the domain, costs $0.05 USDC, is a POST to a named endpoint, and unpaid calls return 402 without running. It also explains the interpretation rule for a dangling name. Missing pieces are auth/token requirements and any hint of the response shape.

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, purpose front-loaded before the caveat, pricing, and transport details. Every sentence carries information; only the bare endpoint string is arguably filler since the transport is implied elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a high-complexity tool: 11 params, 6 required, deep nested objects (records, targets, assignments, certificates, verification), no output schema, and no annotations. Against that surface, the description is thin — it omits the token/auth parameter entirely and never indicates what the audit returns, which for a comparison tool with no output schema is a significant gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and there are 11 parameters, so the description must compensate, but it only loosely names five of them (domain, tenant, TXT records, targets, assignment status). Key inputs like 'token', 'previous', 'checkedAt', 'status', and 'certificates' get no explanation of meaning or role in the audit.

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 opens with a specific verb and enumerates the compared resources: 'Compare a custom domain, tenant, ownership TXT records, DNS targets, and platform assignment status.' That is far more precise than a restatement of the name/title, though it never names a sibling or states what distinguishes it from domain-security_onboarding-readiness or domain-security_infrastructure-health.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through scope constraints: 'The audit does not query DNS or claim the domain' tells the agent this operates on supplied data, not live state. However, there is no explicit when-to-use guidance and no routing to an alternative tool when the caller actually needs live DNS resolution or domain claiming.

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