Skip to main content
Glama

Website: where the new site stands

website_status
Read-onlyIdempotent

Where a client's new website stands: version, design check, the preview, approval and download links, whether the client approved, and any changes the client asked for on the approval link.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely new behavioral context: the response includes links (preview, approval, download), an approval indicator, and client-requested changes, which tells the agent this is a rich status snapshot rather than a boolean check. It does not state what happens when the client has no site or how the client is resolved, which keeps it below 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?

A single dense sentence with the purpose front-loaded and no filler. The colon-list enumeration is efficient for conveying the return shape, though terms like 'design check' and 'version' are unexplained.

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?

There is no output schema, so the description carries the burden of describing the return payload, and it does so well by enumerating the fields an agent will receive. The main gap is the completely undocumented 'client' parameter and error behavior for unknown clients.

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?

Schema description coverage is 0% and there is one required parameter, 'client', whose format (name, slug, ID, email?) is never specified in the description. The phrase 'a client's new website' only weakly implies the parameter refers to a client identifier. With no schema documentation to fall back on, the description should have compensated and does not.

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 the resource precisely ('a client's new website') and enumerates the state it reports: version, design check, preview, approval/download links, approval status, and requested changes. It is clearly a read/status tool, distinguishable from mutating siblings like website_approve or website_launch. It lacks an explicit verb ('get'/'retrieve'), which keeps it just short of 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 Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no named alternatives. The phrase 'where a client's new website stands' implies a progress-check context, but an agent is left to infer whether to call this versus site_health, website_domain_check, or website_approve.

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.