Skip to main content
Glama

owa_hide_screens

Destructive

Hides a presentation screen by ID, or all screens when no ID is given, removing content from the projector. Confirm with the user before calling, since it takes content off the display.

Instructions

Hide one presentation screen by id, or every screen when no id is given. The one destructive-ish action here: it takes content off a projector, so confirm with the user first.

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

Input Schema

NameRequiredDescriptionDefault
screenIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.4/5.0
Behavior4/5

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

The destructiveHint annotation only flags risk; the description adds real context by explaining what is actually at stake (content comes off a projector) and prescribing a confirmation step. It moderates the flag with "destructive-ish," which usefully signals this is a visibility change rather than a deletion. It does not state whether hiding is reversible or how to restore a screen, leaving that gap.

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 sentences, front-loaded with the core action and scope, followed by the safety caveat. No filler and nothing repeated from the schema or annotations.

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 one-parameter tool with no output schema, the description covers the essential unknowns: default behavior when the parameter is absent, the real-world effect, and the required confirmation. The only meaningful omissions are reversibility and the source of screen ids.

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?

Schema coverage is 0%, so the description carries the burden — and it does the most important part: teaching that screenId is optional and that omitting it affects every screen, a behavior the bare optional integer in the schema cannot convey. It does not say where valid ids come from or what an invalid id does.

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 ("Hide one presentation screen by id") and immediately distinguishes the two operating modes: single screen by id, or all screens when no id is supplied. An agent knows exactly what this does and what scope it applies to without opening the schema.

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 clear when-to-use guidance via the parameter-dependent branch (id given = one screen, no id = every screen) and an explicit precondition ("confirm with the user first"). It stops short of naming alternatives such as a list tool for obtaining the id, so it is clear context without explicit exclusions.

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