Skip to main content
Glama
Sign In
cloudflare-mcp

cloudflare-mcp

by jimsimoy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_dns_record

Retrieve a specific DNS record's details by providing its ID and zone ID to inspect configuration or verify settings.

Instructions

Fetch one DNS record's details by its ID within a zone.

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": {
      "zone_id": "<zone_id>",
      "dns_record_id": "<dns_record_id>"
    },
    "name": "get_dns_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
zone_idYes
dns_record_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It clearly indicates a read-only operation ('Fetch') with no side effects, but does not mention potential error responses or authentication requirements.

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 a single, concise sentence that conveys the essential information without redundancy or filler. It is perfectly sized for the tool's simplicity.

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 straightforward nature of a get-by-ID operation, the description is sufficient for an agent to understand what the tool does and what parameters are needed. The presence of an output schema further reduces the need for return-value explanation, though no mention of typical use cases or limitations is made.

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?

Parameter names 'zone_id' and 'dns_record_id' are self-explanatory, and the description provides context ('within a zone' and 'by its ID'). However, there is no explicit definition of each parameter or constraints (e.g., format, requiredness), as schema coverage is 0%.

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?

Description clearly states the action ('Fetch') and the resource ('DNS record') with a specific scope ('by its ID within a zone'). It is easily distinguishable from sibling tools like list_dns_records (bulk retrieval) and create/update/delete (mutations).

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?

The description implies usage when a specific record ID is known, but it does not explicitly state when to prefer this over list_dns_records or other alternatives. No guidance is given for edge cases or prerequisites.

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