Skip to main content
Glama

Website: check the domain and certificate

website_domain_check
Read-onlyIdempotent

Check the client's website domain: whether the TXT record is visible yet, then request its certificate. Safe to call again.

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": {
      "client": "<client>"
    },
    "name": "website_domain_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and "Safe to call again" largely restates idempotency. The description does add useful behavior context by explaining the two-stage nature of the call (TXT visibility first, then certificate request). It does not say what happens when the TXT record is not yet visible (error vs. pending result) or how long certificate issuance takes, and "request its certificate" sits in mild tension with readOnlyHint=true since it implies triggering a provisioning step.

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?

Two short sentences with a front-loaded colon clause that puts the primary check first and the follow-on certificate request second. There is no padding, though "Safe to call again" is slightly vague phrasing for what is really an idempotency note.

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?

For a one-parameter tool with no output schema and annotations that already cover safety and idempotency, the description gives enough to call it correctly: what it checks, what it triggers, and that repetition is safe.

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 0% for the single `client` parameter, so the description must carry the meaning. It clarifies that `client` identifies the client whose website domain is being checked, which is real added meaning, but it does not specify the expected format (client ID, name, or domain).

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 names a specific verb and resource: check the client's website domain, specifically TXT record visibility, and request the certificate. An agent can tell this is a domain-verification step rather than a general site check. It stops short of naming how it differs from the sibling `website_domain` or `website_approve`, so it is not a 5.

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?

"Safe to call again" implies a polling/re-check pattern, and the phrase "whether the TXT record is visible yet" implies it is used after TXT records have been published. However, no explicit when-to-use, when-not-to-use, or alternative (e.g. `website_domain`, `website_status`) is stated, so the usage context must be inferred.

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.