Skip to main content
Glama

Consultar domínio .br

consultar_dominio_br
Read-onlyIdempotent

Check whether a .br domain is available or already registered via Registro.br, returning registration status, expiration date, and suggested alternatives.

Instructions

Verifica no Registro.br se um domínio .br está disponível ou registrado (com data de expiração e sugestões).

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

Input Schema

NameRequiredDescriptionDefault
dominioYesDomínio, ex.: minhaempresa.com.br

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds real context beyond that: it discloses the external source queried (Registro.br) and the shape of the payoff (availability status, expiration date, suggestions). It does not mention failure modes such as malformed or non-.br input.

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?

One front-loaded sentence states the action, the source, and the return content with no filler. Nothing could be removed without losing information.

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 one-parameter read tool with annotations covering safety, the description says what it checks, where, and what comes back, which is sufficient even without an output schema. Only edge-case behavior (invalid or non-.br input, lookups that fail) is unaddressed.

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% for the single parameter, so the baseline would be 3. The description earns the extra point by constraining the input to .br domains, a restriction the schema does not enforce (its example is just 'minhaempresa.com.br').

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 pairs a specific verb ('Verifica') with a specific resource ('domínio .br') and names the source of truth (Registro.br), which is enough to separate it from every sibling (CEP, CNPJ, DDD, ISBN, taxas, FIPE). It does not explicitly route away from any sibling, but the resource itself is unique, so ambiguity is low.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer it is the tool for checking whether a .br domain is free or taken. There is no explicit when-to-use, when-not-to-use, or named alternative, so guidance remains implicit.

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