Skip to main content
Glama

DNSFix

Get my alerts

get_alerts
Read-onlyIdempotent

Recent alerts (changes, problems, expiry warnings, things resolved) for your watched domains, newest first. 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": "get_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional: how many alerts to return, 1 to 100 (default 20)
sinceNoOptional ISO date, for example 2026-11-01
domainNoOptional: only this domain

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Optional: how many alerts to return, 1 to 100 (default 20)"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuinely new context: the result ordering (newest first) and the account/watching prerequisite that gates the call. It stops short of describing behavior on an unconnected account or how results are truncated.

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?

Two short sentences, zero filler, with the core purpose and result ordering front-loaded before the prerequisite. Every clause carries information an agent needs.

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 simple read-only list tool with fully described parameters and no output schema, this is nearly complete: content, ordering, and access prerequisite are all covered. Only the failure mode when no account is connected is left unstated.

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%, so limit, since, and domain are fully documented in the schema. The description only reinforces meaning indirectly via 'newest first' and 'for your watched domains'; it adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 resource (alerts) and enumerates what it contains — changes, problems, expiry warnings, resolutions — plus ordering (newest first) and scope (watched domains). No sibling tool returns alerts, so the agent can identify it immediately.

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?

Provides a real prerequisite: a connected DNSFix™ account with domain watching enabled, which tells the agent when the tool will actually work. However, it offers no explicit when-to-use versus alternatives, and no exclusions or failure behavior when the prerequisite is unmet.

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