Skip to main content
Glama

DNSFix

Get grade history

get_history
Read-onlyIdempotent

Grade and score over time for one of your watched domains. Needs a connected DNSFix™ account with domain watching.

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

Input Schema

NameRequiredDescriptionDefault
daysNoOptional: how many days back to look, 1 to 365 (default 30)
domainYesA domain name, for example yourbusiness.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / days / description
      Added value: +"Optional: how many days back to look, 1 to 365 (default 30)"
  2. First observed

TDQS

A3.6/5.0
Behavior3/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 safety is covered. The description adds a genuine behavioral gate — a linked account and an actively watched domain — but says nothing about what happens if that gate is unmet or about rate/time-series behavior.

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, purpose first and prerequisite second, with no filler. Every clause carries information the 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 two-parameter read with no output schema, purpose plus the account/watching prerequisite is close to sufficient. A note on the returned time-series shape or on the un-watched-domain failure mode would close the remaining gap.

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 description coverage is 100%: the domain format and the 1–365 day window with a 30-day default are fully documented in the schema. The description adds no further parameter meaning, so the baseline 3 applies.

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: grade and score over time for a watched domain. That cleanly separates it from point-in-time siblings like get_domain or get_dmarc_summary, but it never names an alternative outright.

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?

The precondition 'needs a connected DNSFix™ account with domain watching' tells the agent when the call is valid, which is real usage context. There is no guidance on when to prefer this over the other grade/DMARC history-ish siblings, and no explicit exclusions.

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