Skip to main content
Glama

site_status

Check if a website is currently usable by verifying sign-in status and absence of blocking dialogs, returning a screenshot path for visual confirmation.

Instructions

Is the site usable right now (signed in, no blocking dialog)? Returns a screenshot path for a look.

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": {
      "site": "<site>"
    },
    "name": "site_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden. It usefully reveals that the check involves authentication state and dialog detection, and that a screenshot is produced, but it says nothing about whether the call navigates or loads a page, how slow it may be, what happens if the site is unreachable, or what the failure result looks like. For a live-probing tool with zero annotation coverage this leaves real gaps.

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?

Two tight sentences, front-loaded with the question being answered, followed by the return value. The parenthetical definition earns its space by pinning down what 'usable' means.

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 correctly fills in the return value (a screenshot path). However, the ambiguity of the lone 'site' parameter and the total absence of behavioral context (speed, failure modes, side effects of taking a screenshot) mean it is only adequate for an agent to call it correctly the first time.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required parameter 'site' has 0% schema description coverage, and the description never clarifies whether it expects a site name, an identifier from list_sites, or a URL. The description therefore adds no meaning beyond the bare schema.

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 gives a concrete question the tool answers (is the site usable) and defines the criterion in parentheses: signed in with no blocking dialog. That is far more specific than a name restatement, and it is distinguishable from list_sites or thread tools. It stops short of explicitly naming a sibling it replaces.

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

Usage Guidelines2/5

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

The phrase 'right now' hints that this is a live probe rather than a cached lookup, which is mild implicit guidance. There is no statement of when to call it versus list_sites or the other siblings, and no preconditions or when-not-to-use case.

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