Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_get_dns_records

Retrieve DNS records for a domain zone to manage domain configurations and troubleshoot connectivity issues.

Instructions

Get DNS records for a specific zone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zone_nameYesThe zone name/domain

Implementation Reference

  • The definition and handler for 'pressable_get_dns_records'. The handler fetches DNS records for a given zone from the API.
    {
        name: 'pressable_get_dns_records',
        description: 'Get DNS records for a specific zone.',
        inputSchema: {
            type: 'object',
            properties: {
                zone_name: { type: 'string', description: 'The zone name/domain' }
            },
            required: ['zone_name']
        },
        handler: async (args) => {
            return await api.get(`/dns/zones/${args.zone_name}/records`);
        }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. While 'Get' implies a read-only operation, the description discloses no details about what record types are returned, pagination behavior, rate limits, or whether system records are included.

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?

Extremely concise at seven words, front-loaded with the verb 'Get'. No wasted words, though the brevity borders on under-specification given the lack of annotations and output schema.

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

Completeness3/5

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

Adequate for a single-parameter tool with complete schema coverage, but has a clear gap: with no output schema provided, the description fails to specify what data structure or record types are returned, leaving the agent blind to the operation's output.

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?

With 100% schema description coverage for the single `zone_name` parameter, the structured schema already documents the input fully. The description adds no additional semantic details (e.g., format requirements, trailing dot handling) beyond the schema's 'The zone name/domain'.

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 specific verb (Get), resource (DNS records), and scope (for a specific zone). However, it does not explicitly differentiate from sibling `pressable_generate_email_provider_dns_records` or clarify that this retrieves existing records versus generating new ones.

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?

Provides no guidance on when to use this tool versus alternatives like `pressable_generate_email_provider_dns_records`, nor does it mention prerequisites such as zone ownership or necessary permissions.

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