Skip to main content
Glama

Domain check batch

domain_check_batch

Up to 10 link checks in one call. Same signals as domain_check. counts.high is how many not to send a user to. $0.01 per call over x402.

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": "domain_check_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesup to 10 domains or URLs, comma-separated, or a JSON array
paymentNoa signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does a reasonable job: it discloses the batch size cap (10), the per-call price ($0.01 over x402), and explains the key result field counts.high in actionable terms ('how many not to send a user to'). It omits error/failure behavior, whether partial failures are possible within a batch, and any rate limits, which keeps it from a 5.

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?

Four short, front-loaded sentences with zero filler; the batch limit and the sibling relationship come first. The counts.high sentence is telegraphic and slightly opaque out of context, but it earns its place by giving output semantics that are otherwise absent.

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?

There is no output schema and no annotations, so the description is the only source for return-value meaning, yet it explains just one field (counts.high) and not the rest of the response shape. Pricing and the payment-inside-call path are covered, but failure modes for a batch of 10 and the overall result structure remain unstated.

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 schema already explains both the domains (comma-separated or JSON array, up to 10) and payment parameters in more detail than the description. The description adds only the batch-count constraint, which the schema also states. Baseline 3 is appropriate since the schema does the heavy lifting.

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 capability: batch execution of up to 10 link/domain checks in one call, and explicitly ties it to the sibling domain_check by saying it returns the same signals. That lets an agent place it relative to domain_check. The only wrinkle is the resource is called 'link checks' while the tool and sibling are 'domain_check', which is a minor terminology inconsistency rather than ambiguity.

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?

'Same signals as domain_check' and 'Up to 10 ... in one call' imply that this is the bulk variant to use when you have multiple domains instead of one. However, it never states when to prefer it over calling domain_check repeatedly, what happens with more than 10 domains, or any exclusion. Usage is inferable but not spelled out.

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