Skip to main content
Glama

Batch Domain Availability Check

bulk_available
Read-onlyIdempotent

Check the registration status of up to 50 domains at a point in time. Concurrent calls are not supported: send one batch, wait for its result, then send the next; parallel calls are rejected and return no data. available means the domain can be registered; registered means it is already registered; expiring means it is in an expiry-related lifecycle and is not directly registrable; reserved means it is reserved by the registry; unknown means no check produced a reliable conclusion. A failed check does not count as available.

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": {
      "domains": "<domains>"
    },
    "name": "bulk_available"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesComma-separated fully qualified domain names, maximum 50.

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message when success is false.
totalNo
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  2. Changed1 schema field changed
    • changedOutput schema / properties / data / items / properties / price / description
      Previous value: -"Price including currency when supplied by the upstream service."New value: +"Registration price including currency, when available."
  3. Added

TDQS

A3.9/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 still adds real value by disclosing the no-concurrency constraint and the failure semantics ('a failed check does not count as available'). It doesn't cover rate limits, per-domain partial failures within a batch, or what an over-limit input does, but the added concurrency and failure context is substantive.

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?

The constraint-heavy concurrency warning is front-loaded in the second sentence where it matters most, and the status glossary is compactly written as a single semicolon-separated list. The glossary is somewhat long given an output schema exists, but each clause is short and front-loaded with the key term.

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 one-parameter batch read with an output schema and full annotations, the definition covers the important edges: concurrency, timing, status meaning, and failure interpretation. Remaining gaps (rate limits, behavior above 50 domains, partial-batch failures) are minor and arguably beyond an agent's decision needs.

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 coverage, so the schema already documents the comma-separated format and the 50-item maximum. The description reinforces the batch size ('up to 50 domains') and the point-in-time semantics, but adds no syntax or format detail beyond the schema, so 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 ('Check the registration status of up to 50 domains') plus a scope qualifier ('at a point in time'), which is far more informative than the tool name alone. It doesn't explicitly point at the single-domain sibling 'available' as the alternative for one-off checks, so sibling differentiation is left implicit in the word 'bulk' and the 50-domain limit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete operational guidance: send one batch, wait for the result, then send the next, and notes that parallel calls are rejected and return no data. What it lacks is routing guidance against siblings (e.g., use 'available' for a single domain, 'bulk_tld' for TLD-level scans), so an agent must infer when this tool is preferable to the alternatives.

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.