Skip to main content
Glama

Put everything back to normal

release_all
DestructiveIdempotent

End all scenes and all pushed content on the team's screens. Screen mirroring keeps running.

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": "release_all"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuine value beyond that: it specifies exactly what is destroyed (scenes and pushed content) and what survives ('Screen mirroring keeps running'), which is precisely the blast-radius information an agent needs before an irreversible bulk action.

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 short sentences with no waste: the destruction scope is front-loaded and the survival exception follows immediately. Nothing is repeated from the annotations or the schema.

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?

For a zero-parameter, irreversible bulk operation, the description covers what is affected and what is not, which is the core need. It omits confirmation/undo expectations and whether the effect is team-wide or installation-wide beyond 'the team's screens', leaving a small gap for a destructive global action.

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 there is nothing for the description to disambiguate; baseline for a parameterless schema applies. The description correctly implies the target cannot be narrowed and the operation always applies to everything.

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 ('End') and specific resources ('all scenes and all pushed content') with an explicit scope ('the team's screens'). The blanket 'all' plus team-wide scope implicitly distinguishes it from the singular release_scene and release_screen siblings, though it never names or contrasts them directly.

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

Usage Guidelines3/5

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

The bulk 'all ... on the team's screens' framing implies this is the broad reset option versus the narrower release siblings, but there is no explicit statement of when to prefer this tool over release_scene/release_screen and no stated prerequisites or exclusions. Usage must be inferred from scope wording rather than guidance.

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.

Resources