Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_create_dns_record

Create DNS records (A, AAAA, CNAME, MX, TXT, SRV, NS) for domain zones to manage website routing and email configuration.

Instructions

Create a new DNS record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zone_nameYes
typeYes
nameYes
contentYes
priorityNo
ttlNo

Implementation Reference

  • Handler for the pressable_create_dns_record tool.
    handler: async (args) => {
        const { zone_name, ...recordData } = args;
        return await api.post(`/dns/zones/${zone_name}/records`, recordData);
    }
  • Input schema for the pressable_create_dns_record tool.
    inputSchema: {
        type: 'object',
        properties: {
            zone_name: { type: 'string' },
            type: { type: 'string', enum: ['A', 'AAAA', 'CNAME', 'MX', 'TXT', 'SRV', 'NS'] },
            name: { type: 'string' },
            content: { type: 'string' },
            priority: { type: 'integer' },
            ttl: { type: 'integer' }
        },
        required: ['zone_name', 'type', 'name', 'content']
    },
  • tools/dns.js:26-45 (registration)
    Registration of the pressable_create_dns_record tool.
    {
        name: 'pressable_create_dns_record',
        description: 'Create a new DNS record.',
        inputSchema: {
            type: 'object',
            properties: {
                zone_name: { type: 'string' },
                type: { type: 'string', enum: ['A', 'AAAA', 'CNAME', 'MX', 'TXT', 'SRV', 'NS'] },
                name: { type: 'string' },
                content: { type: 'string' },
                priority: { type: 'integer' },
                ttl: { type: 'integer' }
            },
            required: ['zone_name', 'type', 'name', 'content']
        },
        handler: async (args) => {
            const { zone_name, ...recordData } = args;
            return await api.post(`/dns/zones/${zone_name}/records`, recordData);
        }
    },
Behavior2/5

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

With zero annotations provided, the description carries full behavioral disclosure burden but only indicates this is a write operation via 'Create'. It omits propagation timing, atomicity guarantees, permission requirements, and whether the operation is synchronous or queued.

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

Conciseness2/5

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

While physically brief at five words, this represents under-specification masquerading as conciseness. The single sentence adds negligible value beyond the tool name and fails to front-load critical context for a complex infrastructure operation.

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?

For a 6-parameter DNS creation tool with no output schema and complex sibling relationships, the description is grossly incomplete. It lacks zone management context, record type behavioral differences, success/failure semantics, and integration with 'pressable_list_dns_zones' prerequisites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across all 6 parameters, and the description completely fails to compensate. Critical semantics like 'zone_name' (identifier format), 'priority' (MX-specific usage), and 'ttl' (seconds vs minutes) remain undocumented despite the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a new DNS record' essentially restates the tool name 'pressable_create_dns_record' with minimal expansion. While the verb and resource are clear, it fails to distinguish from sibling 'pressable_generate_email_provider_dns_records' or clarify Pressable-specific DNS zone management context.

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

Usage Guidelines1/5

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

Description provides no guidance on when to use this manual creation tool versus the automated 'pressable_generate_email_provider_dns_records', prerequisites such as existing DNS zones, or whether this tool handles duplicate record detection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PCWProps/pressable-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server