Skip to main content
Glama
Sign In
dnsdumpster

dnsdumpster

by MaxWeeden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_cname_records

Retrieve CNAME records for a domain to identify alias or canonical name mappings.

Instructions

Get CNAME records for a domain.

Args:
    domain: The domain name to query (e.g., example.com)
    ctx: Request context

Returns:
    Formatted string containing CNAME records

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

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as authentication requirements, rate limits, or error handling. It only states it returns a formatted string, leaving the agent without safety or constraint information.

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?

The description is extremely concise with no wasted words, fitting all necessary information into a few lines.

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?

Given the tool's simplicity (single parameter, no output schema), the description covers the purpose, parameter usage, and return value adequately. It could mention potential errors, but is sufficient for basic use.

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?

The description adds meaning beyond the raw schema by explaining the 'domain' parameter with an example, compensating for the lack of schema descriptions (0% coverage) and providing useful context.

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 clearly states 'Get CNAME records for a domain' with a specific verb and resource, and distinguishes it from sibling tools like get_a_records and get_mx_records by focusing on CNAME records.

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?

While there is no explicit when-not-to-use guidance, the description and tool name make it obvious that this tool is for CNAME records, and sibling tool names indicate alternatives for other record types.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools