Skip to main content
Glama
Sign In

Gemmein

by com.gemmein
OverviewDiscussionsAdmin

Development: delete a relay

dev_delete_relay
DestructiveIdempotent

Deletes one relay from Development, with its run history — the dashboard's own delete, at once, with no approval: Development's events no longer start it. Never Live: a relay Live has stays in Live, and a promote never removes anything from Live — removing Live's is its own request (request_delete_relay), approved by the founder in their browser. put_relay makes it again. On the founder's Logs.

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

Input Schema

NameRequiredDescriptionDefault
nameYesthe relay's name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint/idempotentHint, but the description adds the context they can't: no approval step, run history is also destroyed, Development events stop starting the relay, Live data is untouched, and the action is recorded on the founder's Logs. This is exactly the added behavioral layer the dimension asks for.

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?

Lead clause front-loads scope and effect, and every sentence carries information. The prose is elliptical and fragmentary ('On the founder's Logs.', 'Never Live'), which costs some readability but not length.

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 destructive single-parameter mutation with no output schema, the description covers scope, approval model, cascade effects, non-effects on Live, recovery, and audit location — nothing an agent needs before calling is missing.

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?

Only one parameter ('name') and schema description coverage is 100%, so the schema already carries the meaning. The description's 'one relay' framing confirms single-target deletion but adds no format or lookup guidance beyond the schema; baseline 3 applies.

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?

States a specific verb and resource with environment scope: deletes one relay from Development along with its run history. It explicitly separates itself from request_delete_relay (Live deletes) and put_relay (recreation), so an agent can place it among siblings without opening schemas.

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?

Gives explicit when-to-use (Development, no approval, immediate) and when-not-to-use (never Live — use request_delete_relay, which is founder-approved in browser). It also names the recovery path (put_relay makes it again), which is a real routing condition.

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