Skip to main content
Glama

Show where a domain points

ver_dns
Read-onlyIdempotent

Use this when someone wants to know where a domain points: its name servers, the records of the domain and of www, its mail servers, and whether it already reaches their palimpalem website. Requires palimpalem sign-in. Read only; changes nothing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "ver_dns"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain, e.g. panaderia-ruzafa.es.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the bar is lower. The description adds the important authentication requirement and enumerates the returned diagnostic categories, which is useful since there is no output schema.

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 front-loaded with the usage condition and keeps every sentence functional. The list of outputs earns its place by compensating for the absence of an output schema.

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

Completeness4/5

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

For a read-only diagnostic tool, the description covers the main inputs, authentication requirement, and categories of results. It could be more specific about record types or what 'reaches their palimpalem website' means, but it is largely complete.

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?

Schema coverage is 100% for the single domain parameter, which includes an example. The description does not add format or validation details beyond the schema, so it sits at the baseline for well-documented parameters.

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 states a specific purpose and enumerates concrete outputs: name servers, domain and www records, mail servers, and whether the domain reaches the user's palimpalem website. It is clear what the tool does, but it does not explicitly differentiate itself from siblings such as comprobar_dominio or ver_mi_web.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The opening phrase 'Use this when someone wants to know where a domain points' gives clear when-to-use guidance. It does not mention when not to use it or name alternative tools, so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.