Skip to main content
Glama
Sign In

Gemmein

by com.gemmein
OverviewDiscussionsAdmin

Turn the preview link off

site_revoke_previews
Destructive

Turns the Development preview's link off, the way the dashboard's Preview link switch does: no link opens the preview, old or new, and every device that opened it is cut off. It stays off: only the founder can open the preview, signed in to Gemmein. site_share_link with on: true turns it back on with a new link (anything shared before stays dead). The site's files and the version it serves don't change. Development only — the Live site is public and has no preview link. Development caps how many a day. On the founder's Logs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "site_revoke_previews"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds genuinely useful context beyond that: existing and new links stop working, open devices are cut off, access reverts to the signed-in founder, files and served version are unchanged, and daily caps apply. It does not describe any return payload or how many links may exist, so a 3 rather than a 5.

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?

The irreversible effect is front-loaded ('no link opens the preview, old or new'), followed by the re-enable path and the Development-only constraint. No sentence is filler; each adds a distinct fact.

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 zero-parameter mutation with no output schema, the description covers side effects, access consequences, reversibility, rate limits, environment scope, and audit logging. Nothing else is needed to invoke it correctly.

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

Parameters4/5

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

The tool takes zero parameters, so the description needn't explain inputs; the baseline for a 0-param tool is 4. Nothing in the description falsely implies configurable options.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Turns the Development preview's link off') and immediately names the sibling it contrasts with, site_share_link. An agent can distinguish this from share/publish/unpublish tools without opening any schema.

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

Usage Guidelines5/5

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

It explicitly scopes usage to the Development site and rules out the Live site ('the Live site is public and has no preview link'), and it names the inverse operation: 'site_share_link with on: true turns it back on with a new link'. Both the when and the alternative are spelled out.

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

All Gemmein toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources