MCP DNS
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dns-queryC | Make a DNS query for a given name and type |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as making DNS queries, leaving no ambiguity for an agent to misselect among alternatives.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name 'dns-query' follows a clear and descriptive pattern, using a hyphen to separate domain and action.
A single tool is generally too few for a DNS server's scope, which typically involves operations like querying, resolving, or managing DNS records. This minimal set feels thin and may limit functionality for agents needing more comprehensive DNS interactions.
The tool surface is severely incomplete for a DNS domain. While 'dns-query' covers basic lookups, there are obvious gaps such as reverse DNS lookups, record management (e.g., adding or deleting records), or handling different DNS server configurations, which could cause agent failures in broader DNS-related tasks.