Skip to main content
Glama

TLDMint Live Domain & DNS MCP

get_verified_domain_coupons

Retrieve verified active Namecheap promo codes and flash sales for domains (.COM $5.98, .STORE $0.98, $0.99 TLDs), EasyWP WordPress, Shared Hosting, Private Email, and FastVPN.

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_verified_domain_coupons"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoOptional product category filter.

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 exist, so the description carries the full behavioral burden. It does add the meaningful qualifiers 'verified' and 'active', implying codes are validated rather than scraped raw, and the retrieval framing implies a read-only operation. It does not disclose freshness/staleness, whether a live API is hit, rate limits, or what a returned coupon record contains.

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?

A single front-loaded sentence with the verb and scope first, then the covered product lines, then illustrative prices. It is dense and wastes few words, though the hard-coded prices ($5.98, $0.98) are volatile detail that may age poorly and could be trimmed.

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?

This is a low-complexity, single-optional-param read tool, so the description is nearly sufficient. However, there is no output schema and the description never indicates the shape of a returned coupon (code, discount, expiry, category, source URL), which the agent would need to render results sensibly.

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% and the single parameter is an enum with a clear 'Optional product category filter' description, so the schema already does the work. The description's category list (domains, WordPress, hosting, email, VPN) loosely maps to the enum values but does not explain default behavior when the filter is omitted (presumably 'all'). 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?

The description states a specific verb (retrieve) and resource (verified active Namecheap promo codes and flash sales) with concrete scope: domains, EasyWP, Shared Hosting, Private Email, FastVPN. That is far more specific than the tool name alone and clearly distinct from siblings like check_domain_availability or inspect_domain_dns_whois. It stops short of a 5 because it never explicitly contrasts itself with those siblings, leaving the agent to infer non-overlap.

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?

There is no explicit when-to-use, when-not-to-use, or alternative named. Usage is only implied by the enumerated product categories, from which an agent infers 'call this when the user wants current discounts before purchasing.' That is adequate for a simple read tool but is inference rather than guidance.

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.