Skip to main content
Glama
Sign In
Geekflare

Geekflare

Official
by geekflare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

dnsRecord

Retrieve DNS records for a domain to inspect A, AAAA, CNAME, MX, NS, SOA, TXT, CAA, and SRV record types.

Instructions

Retrieve DNS records for a domain

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

Input Schema

NameRequiredDescriptionDefault
urlYesTarget URL
typesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.4

TDQS

C2.9/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 behavioral traits such as read-only nature, error handling, or rate limiting. The bare description leaves the agent without critical operational context.

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 description is a single sentence, free of fluff. While it could be more structured (e.g., listing parameters), it achieves conciseness without extraneous content.

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?

With 2 parameters, no output schema, and no annotations, the description does not provide enough context. It omits what the output looks like, default behavior for 'types', and error conditions.

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 coverage is 50%; only 'url' has a description ('Target URL'). 'types' lacks any description in the schema, and the tool description adds no extra meaning. With limited schema detail, the description fails to compensate.

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 'Retrieve DNS records for a domain' with a specific verb and resource. It distinguishes well from sibling tools like dnsSec, which likely focus on security records.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like dnsSec or other diagnostic tools. The agent receives no context for selection.

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