Skip to main content
Glama

incognito

Toggle private playback mode to stop plays from being saved to history, including CLI- and AI-started playback. Call with no arguments to read its current state.

Instructions

Read or set incognito mode. While on, nothing is written to the play history — including plays started from the CLI or by you. Call with no arguments to read it.

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

Input Schema

NameRequiredDescriptionDefault
enabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden, and it delivers the key non-obvious effect: nothing is written to the play history while the mode is on. It goes further to clarify that this covers plays started from the CLI or by the agent itself, which is exactly the kind of scope detail an agent could otherwise get wrong. It does not say whether the setting persists across sessions or is scoped per workspace.

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?

Three short sentences, zero waste, with the core capability front-loaded and the invocation rule last. The em-dash aside about CLI and agent-originated plays earns its place by removing a real ambiguity.

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-boolean toggle with no output schema and no annotations, this covers what an agent needs: what it does, the side effect, its scope, and how to read it. The only gap is persistence and the shape of the read response, both minor for a boolean state flag.

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 description coverage is 0%, so the description must define the single parameter's role, and it does so indirectly by telling the agent to omit arguments to read. That establishes the omitted-vs-supplied semantics, but it never states what a supplied value does or what the read returns, so some inference remains over the schema's bare `enabled` boolean.

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?

The description names a specific verb pair and resource: 'Read or set incognito mode'. The dual read/write nature is stated up front, so an agent knows exactly what the tool targets. No sibling differentiator is named, but no sibling in the catalog plausibly overlaps with incognito state, making this clear without needing one.

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?

'Call with no arguments to read it' explicitly disambiguates the read case from the set case, which is the main selection decision an agent faces with this tool. There is no when-not-to-use guidance, but with a single toggle and no competing siblings there is little to exclude.

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

Deploy Server

Other Tools