Pressable MCP Server

Overview Schema Source Related Servers Discussions Admin

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

Name	Required	Description	Default
`zone_name`	Yes
`type`	Yes
`name`	Yes
`content`	Yes
`priority`	No
`ttl`	No

Implementation Reference

tools/dns.js:41-44 (handler)

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);
}

tools/dns.js:29-40 (schema)

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);
    }
},

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 24, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only paraphrases the action ('Create a new DNS record') without revealing side effects, idempotency, validation rules, or permissions. This adds no insight beyond the tool name.

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 concise sentence with no redundant words. It is front-loaded and easy to scan. However, it essentially restates the tool name, so it adds minimal new information, preventing a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has six parameters (four required) and no output schema, but the description provides no context about parameter relationships, required formats, or what the response will contain. It is completely inadequate for understanding how to invoke the tool correctly.

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%, and the description does not explain any of the six parameters. Critical fields like 'name', 'content', and 'type' are left undefined, making it impossible for an agent to know what values to provide. The description fails to compensate for the schema's lack of explanations.

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 'Create a new DNS record' uses a specific verb and resource, clearly distinguishing it from sibling tools like pressable_get_dns_records and pressable_delete_dns_record. The purpose is immediately obvious and unambiguous.

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?

The description provides no guidance on when to use this tool relative to alternatives. It doesn't mention exclusions, prerequisites, or contrast with get/delete/generate DNS record operations. The user is left to infer usage solely from the name.

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

Deploy Server