Skip to main content
Glama

Put a screen back to normal

release_screen
DestructiveIdempotent

End pushed content or a scene on one screen or sub-screen; it goes back to its own content.

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

Input Schema

NameRequiredDescriptionDefault
screen_idYesId of the screen, as listed with the team's screens.
subscreen_idNoId of one sub-screen of a split screen. Leave out to put the whole screen back to normal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / screen_id / description
      Added value: +"Id of the screen, as listed with the team's screens."
    • addedInput schema / properties / subscreen_id / description
      Added value: +"Id of one sub-screen of a split screen. Leave out to put the whole screen back to normal."
  2. First observed

TDQS

A3.8/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 openWorldHint=true, so the safety profile is covered. The description adds the meaningful behavior the annotations cannot convey: what actually happens (pushed content or scene is ended, the screen reverts to its own content). It stops short of stating reversibility beyond the implied re-push, or error behavior for an already-clean screen.

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?

A single compact sentence that front-loads the action and ends with the observable outcome. No filler and nothing redundant with the schema or title.

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 two-parameter mutation tool with rich annotations and full schema coverage, the description covers the essential effect of the call. Only minor gaps remain, such as whether the operation fails or no-ops when nothing is pushed, and how it differs from the scene-wide release siblings.

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 100%, with both screen_id and subscreen_id fully documented in-schema, so the baseline is 3. The description's 'on one screen or sub-screen' corroborates the scope but adds no format or edge-case detail beyond the schema.

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: 'End pushed content or a scene on one screen or sub-screen', plus the resulting state ('goes back to its own content'). It is clear what the tool does, though it never names the closely related siblings (release_all, release_scene) that an agent would need to distinguish it from.

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?

Usage is only implied: 'End pushed content' suggests this is the inverse of push_content, and the sub-screen wording hints at the per-screen scope. There is no explicit when-to-use versus release_scene or release_all, and no stated preconditions.

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