Skip to main content
Glama
Sign In
mcp-cloudflare-crunchtools

mcp-cloudflare-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Dns Record Tool

get_dns_record_tool
Read-only

Retrieve a specific Cloudflare DNS record by its zone ID and record ID. Returns detailed record information.

Instructions

Get a single DNS record by ID.

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>",
      "record_id": "<record_id>"
    },
    "name": "get_dns_record_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
zone_idYesZone ID (32-character hex string)
record_idYesDNS record ID (32-character hex string)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / record_id / description
      Added value: +"DNS record ID (32-character hex string)"
    • addedInput schema / properties / zone_id / description
      Added value: +"Zone ID (32-character hex string)"
  2. Changed3 schema fields changedv0.5.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / record_id / description
      Removed value: -"DNS record ID (32-character hex string)"
    • removedInput schema / properties / zone_id / description
      Removed value: -"Zone ID (32-character hex string)"
  3. First observedv0.5.0

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered without the description. Beyond that the description adds nothing behavioral: no error behavior for a missing/invalid ID, no note on what the record payload contains, no rate-limit context.

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 short sentence with the key scoping qualifier ('single', 'by ID') front-loaded. Nothing is padded or redundant.

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 simple two-parameter read tool with a complete schema, an output schema, and annotations covering safety, the description covers enough to invoke correctly. Only the absence of error/edge-case guidance keeps it from being fully complete.

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%, so both zone_id and record_id (including their hex-string format) are fully documented in the schema. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('Get a single DNS record by ID'), and the word 'single' implicitly separates it from the sibling list_dns_records_tool. It stops short of naming that sibling or contrasting the two, so it is clear but not fully differentiated.

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 phrase 'by ID' implies the caller must already hold a record_id and wants one record rather than a listing, which is a usable signal. But there is no explicit statement of when to prefer this over list_dns_records_tool or get_zone_tool, and no prerequisites given.

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