Skip to main content
Glama

DNSFix

Look up DNS records

lookup_dns
Read-onlyIdempotent

Looks up one record type for a name, with each record's time to live and whether it is signed with DNSSEC.

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": {
      "name": "<name>"
    },
    "name": "lookup_dns"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesA DNS name, for example yourbusiness.com or _dmarc.yourbusiness.com
typeNoRecord type (default A)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing what comes back (TTL and DNSSEC signing status), but says nothing about failure behavior for nonexistent names, empty record sets, or rate limits on the open network.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler; the scope constraint comes first and the return details follow. Nothing is repeated from the title or schema.

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?

For a two-parameter read-only lookup with no output schema, the description covers the essential scope and the shape of the result (per-record TTL and DNSSEC status). It could say more about empty or error results, but little else is needed to call it correctly.

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 coverage is 100% with an enum on 'type' and a documented default of A, so the schema does the heavy lifting. The description only reinforces that exactly one record type is queried at a time, adding marginal meaning beyond the structured fields.

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 gives a specific verb and resource ('Looks up one record type for a name') and clarifies scope: a single record type per call, not a full domain audit. That implicitly separates it from siblings like check_dmarc or check_propagation, though no sibling is named explicitly.

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?

Usage is only implied by the phrase 'one record type for a name'; there is no explicit statement of when to prefer this over check_record or the specialized check_* tools, and no exclusion cases. An agent can infer the generic-lookup use case but must guess at the boundary.

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