Skip to main content
Glama

DNSFix

What should I fix next

what_to_fix_next
Read-onlyIdempotent

Picks the one thing to fix next across your watched domains (or one domain you name), most urgent first: what is wrong, why it matters, the record to paste and the fix guide link, then the next few after it. Read-only: nothing is changed, and the domain owner makes the change at their DNS host. Needs a connected DNSFix™ account with domain watching.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "what_to_fix_next"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoOptional: only this watched domain

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered; the description still adds real context by stating the domain owner must apply the change at their DNS host (explaining why the tool never mutates) and naming the account/watching prerequisite. It also describes the return contents, which matters since there is no output schema. Minor redundancy in restating "read-only: nothing is changed."

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?

Front-loaded with the core action and the ordering guarantee, followed by the payload and then constraints. Only the "Read-only: nothing is changed" clause duplicates what readOnlyHint already asserts, which is the one piece of waste.

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 zero-required-param, one-parameter tool with no output schema, the description covers the essentials: what it returns, ordering, scope default, and the account prerequisite. A brief note on limits of the "next few" follow-ups would make it fully self-sufficient.

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% and the single optional `domain` parameter is already documented, so the baseline would be 3. The description adds the omitted-parameter behavior — that with no domain it spans all watched domains — which the schema does not state.

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?

Names a specific action and scope: picks the single most urgent fix across watched domains (or one named domain), and enumerates the payload (what is wrong, why it matters, record to paste, guide link, plus the next few). This clearly separates it from single-record checks like check_spf or check_dkim.

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?

Implies the right usage context: reach for this when you want a prioritized remediation queue rather than a single check, and it states the precondition (connected DNSFix™ account with domain watching). It does not explicitly say when not to use it or name a sibling alternative, so it falls short of a 5.

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