Skip to main content
Glama

DomainKits

by io.github.ABTdomain

Usage and Quota

usage
Read-onlyIdempotent

Return the current account tier, per-tool-group usage, rate limits, and stateful Monitor and Strategy quotas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierYesAccount tier.
toolsYesUsage and quota information grouped by tools that share a limit.
monitorYes
strategyYes
upgrade_hintNoOptional account-capacity information for tiers that have an upgrade path.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful context by enumerating the exact categories returned (tier, usage, rate limits, quotas) and notes that Monitor and Strategy quotas are 'stateful,' which is useful behavioral insight beyond the annotations.

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?

A single, front-loaded sentence contains zero filler and conveys the full purpose. Every element earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the zero-parameter complexity and the presence of an output schema, the description sufficiently covers what the tool returns. No further details about return value structure are needed, and the description is complete for an agent to select and invoke the tool correctly.

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?

The tool has zero parameters, so the description does not need to explain any. Baseline 4 is appropriate because no parameter guidance is required.

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?

The description uses a specific verb 'Return' and clearly identifies the resource as 'current account tier, per-tool-group usage, rate limits, and stateful Monitor and Strategy quotas.' This precisely distinguishes the tool from siblings like 'monitor' and 'strategy' by framing it as the quota/usage overview.

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 description implies usage for checking account-level limits and quotas but provides no explicit 'when to use' vs alternatives or exclusions. An agent can infer the use case, but the tool does not state when it should be preferred over other information-gathering tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DomainKits toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation3/5

Many domain-search tools (active, aged, expired, deleted, market, nrds, nrds_live) have overlapping boundaries that depend on subtle lifecycle or listing distinctions, and pairs like bulk_tld/tld_check and nrds/nrds_live are easy to confuse. The detailed descriptions and related-tool hints help, but an agent still faces several nearly interchangeable choices.

Naming Consistency4/5

All tool names follow a consistent lowercase_snake_case convention, with no mixing of camelCase or inconsistent verb styles. However, the names use a noun/adjective pattern rather than a clear verb_noun action pattern, and acronyms like nrds, epp_status, and tld_rank make some names less predictable.

Tool Count2/5

32 tools is heavy for a domain toolkit, and several tools are close variants of the same search or check operation, such as active/aged/expired/deleted/market and nrds/nrds_live. The broad domain scope justifies some breadth, but the set would be much more focused with consolidation.

Completeness4/5

The toolset covers the core domain lifecycle well: availability, registration states, WHOIS, DNS, pricing, TLD statistics, safety, backlinks, typosquatting, and monitoring. The main gaps are that strategy can store data but has no retrieval or deletion action, and market pricing is limited to Sedo only.

Resources