Skip to main content
Glama

continental.net Expiring Domains

Get one domain

get_domain
Read-only

Everything we know about one domain on the list: metrics, state, drop date, Clean Score with reasons, Wayback history (first/last year, titles, language).

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

Input Schema

NameRequiredDescriptionDefault
domainYese.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds value by disclosing the payload's content scope (metrics, drop date, Clean Score with reasons, Wayback history), but says nothing about behavior for a domain not on the list, which is the one edge case an agent would need to anticipate.

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 no filler; the parenthetical enumerations add information density without bloat. The dense field list is slightly clumped but each item conveys what the agent will receive.

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 one-parameter read tool with safety annotations already supplied and no output schema, the description does the needed work by enumerating return fields. The minor gap is the unstated error/empty behavior for domains not on the list.

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?

There is a single parameter with 100% schema description coverage ("e.g. example.com"), so the schema already carries the format example. The description adds no input semantics beyond the schema, which is the expected baseline when coverage is complete.

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?

"Everything we know about one domain" states a specific resource and scope (single-domain detail) and enumerates the returned fields (metrics, state, drop date, Clean Score, Wayback history), so the agent knows exactly what the tool retrieves. It stops short of naming drop_stats or search_expiring_domains, so sibling differentiation is left to the tool names rather than the description.

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 phrase "one domain on the list" implies the tool is for domains already in the monitored list, which is useful context, but there is no explicit when-to-use guidance, no when-not-to-use, and no routing to drop_stats or search_expiring_domains for aggregate or search needs. Usage is only implied.

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