Skip to main content
Glama

BRAINIAC Domain Security

Score custom domain readiness

domain-security_onboarding-readiness

Compare the supplied TXT name and token, the CNAME target, and a certificate flag. Readiness drops when the token is missing from the expected name, the CNAME does not match the target, or the certificate flag is false. The hijacking index rises when a CNAME points elsewhere, the token sits on another name, or the certificate does not cover the domain. No DNS lookup is performed. Price $0.04 USDC. POST /api/v1/domain-security/onboarding-readiness. 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>",
      "token": "<token>",
      "txt_name": "<txt_name>",
      "cname_target": "<cname_target>",
      "certificate_covers_domain": "<certificate_covers_domain>",
      "records": "<records>"
    },
    "name": "domain-security_onboarding-readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
domainYes
recordsYes
txt_nameYes
cname_targetYes
certificate_covers_domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses that no DNS lookup happens, states the price ($0.04 USDC), the endpoint, and that unpaid calls return 402 without running. It stops short of stating that the operation is pure/read-only with no side effects, and it gives no indication of what the response payload looks like even though there is no output schema.

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?

The scoring rules are front-loaded ahead of commercial details (price, endpoint, 402 behavior), which is the right priority order. It is dense but every sentence contributes; the only mild sprawl is the parallel 'readiness drops...' / 'hijacking index rises...' pair, which is justified by covering two distinct outputs.

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

Completeness3/5

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

For a 6-parameter, all-required computation tool with no annotations and no output schema, the definition covers the scoring logic and payment semantics but omits the shape of the result (field names, numeric ranges, whether higher readiness is better or what thresholds mean) and says nothing about the `records` collection. An agent can call it correctly but cannot anticipate what comes back.

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 0%, so the description must compensate and it only partly does. It gives operational meaning to the token/TXT matching, the CNAME comparison, and the certificate flag, but the required `records` array (the actual DNS records being evaluated, with TXT/CNAME typing) and the `domain` parameter are never explained, leaving the most structurally complex input undocumented.

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 inputs ('Compare the supplied TXT name and token, the CNAME target, and a certificate flag') and states the two outputs it produces: a readiness score and a hijacking index. That distinguishes it from the sibling 'audit' tools, which are not described as scoring supplied records, but it never explicitly contrasts itself with them.

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?

'No DNS lookup is performed' implicitly tells the agent this tool scores data it already holds rather than fetching anything, which is useful routing context. However, there is no explicit when-to-use or when-not-to-use statement, and no alternative is named for the case where the caller has no records yet and needs a live lookup.

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