Skip to main content
Glama

Check a domain name

comprobar_dominio
Read-onlyIdempotent

Use this when someone wants to know whether a domain name for their website is free, e.g. panaderia-ruzafa. Checks up to three endings (com, es, net, info, org, de, eu) per call; at most one of them is confirmed with the registry, the others are marked as not confirmed. Read only; registers nothing and gives no prices. Limited to a few calls per hour.

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": {
      "name": "<name>"
    },
    "name": "comprobar_dominio"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe name without ending, e.g. panaderia-ruzafa. A full domain such as panaderia-ruzafa.es is also accepted. Letters a-z, digits and hyphens.
endingNoOptional. One ending to check. Without it, com, es and net are checked.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, so the safety bar is low; the description still adds real value by disclosing that at most one ending is actually confirmed with the registry while the rest are marked unconfirmed, and that usage is rate limited to a few calls per hour. That registry-confirmation caveat is behavior an agent would otherwise misreport to a user.

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?

Three short sentences, front-loaded with the use case, then the per-call limit, then the read-only/pricing caveats and rate limit. No sentence is redundant and nothing important is buried.

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

Completeness5/5

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

For a two-parameter read-only check with full schema coverage and annotations covering safety, the description supplies everything else an agent needs: when to use it, how many endings are checked, why results may be partially unconfirmed, and the throttling limit. No output schema exists, and the confirmed/not-confirmed framing already conveys the shape of the result.

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?

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by explaining that 'ending' is capped at one ending per call and that the default check covers three endings, which clarifies the effect of omitting the optional parameter. It does not document the a-z/digit/hyphen format constraint, but the schema already does.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and object ('know whether a domain name for their website is free') with a concrete example, and the resource (domain availability) is plainly distinct from all the website-drafting/publishing siblings. An agent can tell what this does and what it does not do (registration, pricing) without opening the schema.

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?

Gives a clear trigger condition ('when someone wants to know whether a domain name... is free') and implicitly excludes adjacent intents by saying it 'registers nothing and gives no prices'. No alternative tool is named, but no sibling appears to cover domain checking, so the guidance is adequate rather than exhaustive.

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.