Skip to main content
Glama

ramadasmr-networkcalc-mcp

by ai.smithery
OverviewDiscussionsAdmin

dns_lookup

Fetch DNS info for a given domain

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / domain / description
      Added value: +"Domain to look up"
    • removedInput schema / properties / domain / title
      Removed value: -"Domain"
    • removedInput schema / title
      Removed value: -"dns_lookupArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "dns_lookupOutput",
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

C2.9/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 the full burden of behavioral disclosure. It fails to specify what DNS record types are returned (A, MX, NS, etc.), whether the lookup is recursive, rate limiting, or error handling for non-existent domains. The word 'Fetch' implies read-only access but does not explicitly confirm safety or side effects.

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 extremely brief (6 words) and front-loaded with the core action. While it avoids verbosity, it may be excessively minimal—lacking any supporting context about output format or scope that would help an agent predict the tool's utility.

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?

Given the absence of an output schema, the description should ideally characterize the returned DNS information (record types, structure). Without annotations to provide safety hints or output metadata, the description leaves significant gaps in the agent's understanding of the tool's full contract.

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 'domain' parameter, the schema adequately documents the input. The description provides minimal additional semantic context beyond the schema's 'Domain to look up', meeting the baseline expectation but not adding clarifying examples or format details.

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 clearly states the action (Fetch) and resource (DNS info for a domain). However, it does not explicitly distinguish from the sibling tool spf_lookup, which also performs DNS lookups but for a specific record type. A higher score would clarify this distinction.

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 like spf_lookup (for SPF records specifically) or certificate_info. There are no stated prerequisites, exclusions, or conditions that would help an agent select this tool appropriately.

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

All ramadasmr-networkcalc-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources