Skip to main content
Glama

isup_check

Read-onlyIdempotent

Check whether a website or domain is up or down via isitup.org to verify availability before browsing or automating access.

Instructions

Check if a website/domain is up or down via isitup.org.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to check (e.g. google.com).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, and the description corroborates the open-world nature by naming the third-party provider. It does not disclose what a result looks like (e.g. boolean up/down vs. status text) or any rate limits, leaving some behavioral gaps.

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 zero filler. It is efficient, though its brevity comes at the cost of not saying anything about the response.

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?

With no output schema, the description should indicate what the check returns (up/down, response time, HTTP status). That return-shape gap is the main incompleteness for an otherwise simple tool.

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 including an example (google.com), so the schema carries the meaning. The description adds nothing beyond it, which is the expected baseline here.

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 (check) and resource (website/domain up or down), plus the upstream provider isitup.org. It is clear on its own, though it does not explicitly distinguish itself from availability-adjacent siblings like uptimerobot_get_monitors or mc_server_status.

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 narrow phrasing implies when it applies (quick external uptime check), but there is no explicit when-to-use/when-not-to-use statement and no alternative tool named. The mention of isitup.org at least signals the external dependency.

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

Deploy Server

Other Tools