Skip to main content
Glama
Sign In
Glitchrupt MCP Server

Glitchrupt MCP Server

by elbee19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

glitchrupt_wait_for_approval

Register an approval wait that plays recurring desktop glitch cues every 15 minutes until resolved, returning registration rather than playback completion.

Instructions

Register an actual wait on the user's approval. Plays two complete 600 ms glitches separated by 200 ms; repeats every 15 minutes until resolved. Reusing the same key is idempotent and does not replay or reset its timer. Returns registration, not completed playback.

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

Input Schema

NameRequiredDescriptionDefault
keyYes
soundNo
volumeNo
previewNo
variantNoclassic

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: exact glitch timing, 15-minute repetition, idempotency semantics for the same key, and the fact that it returns registration rather than completed playback. This directly clarifies what the tool does and does not do during a wait.

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?

The description is four sentences, front-loads the core action, and every sentence adds relevant operational detail. There is no repetitive or wasted language.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and the description correctly frames the return as registration rather than completed playback, so return-value explanation is not needed. However, with 0% schema description coverage and four undocumented optional parameters, the definition is not fully complete for invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 compensate for five parameters, but it only explains the 'key' parameter indirectly through idempotency. It says nothing about 'sound,' 'volume,' 'preview,' or the 'variant' enum options, leaving most parameter meaning to inference.

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 states a specific action and resource: registering a wait on the user's approval, with playback behavior and repetition. It is clear enough to distinguish from status and resolve tools, but it does not explicitly contrast itself with siblings such as glitchrupt_pending_approvals.

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 implied by 'wait on the user's approval' and 'until resolved,' but the description gives no explicit when-to-use guidance, exclusions, or named alternatives among the sibling tools. An agent can infer the context but is not routed deliberately.

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