Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

CAA record check

caa
Read-onlyIdempotent

Use when the user asks which certificate authorities may issue SSL certificates for a domain, or why issuance is refused. Returns CAA issuers for normal and wildcard certificates and iodef, from parents too. Ex: 'Can Let's Encrypt issue for example.com?'. Free trial without an API key: a few calls a day.

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": "caa"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesA public domain name, e.g. example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare this a safe, read-only, idempotent, open-world query, so the bar is lower; the description still adds real value by explaining that results include wildcard issuers, iodef entries, and inherited records from parent domains. It also discloses the auth/quota profile ('free trial without an API key: a few calls a day'), which the annotations do not cover.

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 definition is four short sentences with the trigger front-loaded, followed by return scope, an example, and the quota note. Every sentence carries information; the example question slightly overlaps the opening trigger sentence but usefully disambiguates intent.

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?

For a single-parameter read-only DNS lookup with no output schema, the description covers the trigger, what the response contains (normal, wildcard, iodef, parent inheritance), and access constraints. Nothing an agent needs in order to call it correctly is missing.

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?

There is only one parameter and the schema documents it at 100% coverage ('A public domain name, e.g. example.com'). The description adds no syntax or format detail beyond that, so the baseline of 3 applies with the schema doing the heavy lifting.

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 description opens with a specific verb and resource: it returns the CAA issuers that may issue SSL certificates for a domain. It also clarifies scope ('for normal and wildcard certificates and iodef, from parents too'), which separates it cleanly from the mail/DNS siblings in the catalog.

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?

It gives an explicit trigger ('Use when the user asks which certificate authorities may issue... or why issuance is refused') and a concrete example question, so the agent knows when this tool is the right call. It does not name alternatives or exclusions, but no other sibling covers CAA records, so the omission is minor.

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.