Skip to main content
Glama

net_tools_email_auth_check

[$x402 pago por llamada] Busca registros SPF y DMARC de un dominio por TXT lookup. No incluye DKIM (su selector es específico de cada proveedor de correo, no tiene ubicación fija).

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

Input Schema

NameRequiredDescriptionDefault
hostYes
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations, so the description carries the full behavioral burden. It does disclose a meaningful trait beyond the schema: this is a paid, per-call endpoint. But it says nothing about what a lookup returns, how missing records are reported, or the 402 flow beyond the schema's own note.

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?

Two sentences, front-loaded with the cost marker and the core action, followed by a scoped exclusion. The parenthetical DKIM explanation earns its place by preventing a wrong call, though it could be shorter.

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

Completeness3/5

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

For a two-parameter read tool with no output schema and no annotations, the description covers purpose, cost model and scope, which is decent. It still leaves the return shape, record-not-found behavior and the undocumented host parameter unaddressed.

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 50%: the payment parameter is documented, while 'host' has no description in either schema or description. The description implies host is a domain name and flags the pay-per-call model, which partially compensates, but it does not state the expected input format for host.

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?

States a specific verb and resource: look up SPF and DMARC records for a domain via TXT lookup. It also pre-empts the most likely confusion by explaining that DKIM is excluded and why. It does not explicitly name the nearest sibling (net_tools_dns_lookup), so an agent must infer the boundary itself.

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: this is the tool for checking a domain's email-authentication posture. The DKIM exclusion is a useful scope boundary, but there is no explicit when-to-use versus dns_lookup or blacklist_check, and no prerequisites stated.

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.

Resources