RequestRepo MCP

by hofill

Overview Schema Source Related Servers Discussions Admin

Python

Remote

list_dns

Retrieve and display DNS records from RequestRepo MCP to inspect domain configurations and manage network settings.

Instructions

List DNS records.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_dns"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/requestrepo_mcp/server.py:187-192 (handler)
The list_dns handler implementation in RequestrepoMCPService class. It fetches DNS records from the requestrepo client using the dns() method and returns them serialized with a count.
```
def list_dns(self) -> dict[str, Any]:
    records = self._client().dns()
    return {
        "count": len(records),
        "records": [serialize_dns_record(record) for record in records],
    }
```
src/requestrepo_mcp/server.py:412-415 (registration)
The list_dns tool registration using FastMCP's @mcp.tool() decorator. This exposes the list_dns functionality as an MCP tool with the description 'List DNS records.'
```
@mcp.tool()
def list_dns() -> dict[str, Any]:
    """List DNS records."""
    return resolved_service.list_dns()
```
src/requestrepo_mcp/serializers.py:40-45 (helper)
The serialize_dns_record helper function that converts a DnsRecord object into a dictionary representation with type, domain, and value fields. Used by list_dns to format output.
```
def serialize_dns_record(record: DnsRecord) -> dict[str, str]:
    return {
        "type": record.type,
        "domain": record.domain,
        "value": record.value,
    }
```
src/requestrepo_mcp/schemas.py:10-10 (schema)
The DnsRecordType schema definition (Literal type with valid DNS record types A, AAAA, CNAME, TXT). Used by other DNS tools like add_dns, remove_dns, and update_dns.
```
DnsRecordType = Literal["A", "AAAA", "CNAME", "TXT"]
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Feb 21, 2026

TDQS

B3.2/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 burden for behavioral disclosure. 'List DNS records' implies a read operation, but it doesn't specify whether this requires authentication, returns all records or a subset, includes pagination, or has rate limits. This is a significant gap for a tool with zero annotation coverage.

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, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it highly concise and well-structured for quick understanding.

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?

Given the tool's simplicity (0 parameters, output schema exists), the description is minimally adequate. However, with no annotations and siblings like 'add_dns' and 'update_dns', it lacks context on permissions, scope, or differences from other tools, leaving gaps in completeness for the agent.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is applied since the schema fully handles parameters, and the description doesn't need to compensate.

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?

The description 'List DNS records' clearly states the verb ('List') and resource ('DNS records'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_files' or 'list_requests' beyond the DNS domain, which prevents a perfect score.

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 versus alternatives. With siblings like 'add_dns', 'remove_dns', and 'update_dns' available, there's no indication of whether this is for read-only operations or how it differs from other listing tools, leaving the agent without usage context.

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

Deploy Server