Skip to main content
Glama

Website: approve the preview

website_approve
DestructiveIdempotent

The agency approves the client's website preview itself (instead of the client's approval link). Call without confirm to see what will be approved, then confirm: true once the agency says yes.

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

Input Schema

NameRequiredDescriptionDefault
clientYes
confirmNoLeave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change.

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 destructiveHint=true, idempotentHint=true, and readOnlyHint=false; the description adds genuine value by explaining the no-op preview mode and that nothing changes until confirm is true. However, it never says what approval actually causes (publishing the site, notifying the client) or why the operation is flagged destructive and open-world, so the consequences of the irreversible step remain opaque.

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 tight sentences with the actor and action front-loaded and the confirm workflow immediately after. The parenthetical is slightly awkward but earns its place by removing ambiguity about who is approving.

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?

For a destructive, open-world mutation with no output schema, the description covers the safety workflow but omits what the tool returns on preview versus confirm and what state the site ends up in. The undocumented required client parameter is also left entirely to inference.

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 coverage is 50%: confirm is fully documented in the schema and the description reinforces its meaning in workflow terms. The required client parameter has no description anywhere, so the agent gets no guidance on whether it expects an ID, domain, or name.

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 and resource ("approves the client's website preview") and disambiguates it from the client-facing approval-link path, which is a real source of confusion. It does not distinguish itself from adjacent siblings such as website_launch, but the core action is unambiguous.

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

Usage Guidelines4/5

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

Gives an explicit two-step workflow: call without confirm to preview, then set confirm: true only once the agency agrees. That is clear conditional guidance, though it is silent on prerequisites (must a preview exist, must the site be launched first) and on alternatives outside this tool.

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.