Skip to main content
Glama
Sign In

CrunchJunkie

by io.crunchjunkie.app
OverviewDiscussionsAdmin

resolve_signal

Move one signal in the Signals inbox, exactly as its buttons do: "resolve" (dealt with), "acknowledge" (seen, still open), "snooze" (hidden for snoozeDays — 1 to 90, default 7 — then open again) or "reopen" (back to new). Reversible: reopen undoes any of them. It does not change the data behind the signal, and a new occurrence is raised again by the detector. Requires MCP write actions; without confirm:true it returns a preview and changes nothing.

Input Schema

NameRequiredDescriptionDefault
actionYesresolve, acknowledge, snooze or reopen.
confirmNoSet true to apply. Omit for a preview. With confirm:true, also pass the preview's previewToken.
signalIdYesThe signal (id from get_signals).
snoozeDaysNosnooze only: days to hide it (default 7).
previewTokenNoWith confirm:true: the previewToken from this tool's preview (valid 15 minutes, once, for exactly the previewed arguments).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond annotations by disclosing reversibility, that underlying signal data is unchanged, that detectors may raise new occurrences, and that confirm:true is required to apply changes while omission returns a preview.

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?

Front-loads the core purpose and action list, then adds only necessary behavioral and safety details. Despite density, every sentence contributes useful information.

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

Completeness5/5

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

Complete for a no-output mutation tool: it covers action semantics, reversibility, data effects, preview/confirm requirements, and the relevant sibling for retrieving signal 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 100%, so baseline is 3, but the description adds meaning to the action enum and snooze behavior beyond the schema's terse parameter descriptions. It also clarifies the confirm preview workflow.

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: move one signal in the Signals inbox, and enumerates the exact actions it performs. It also references get_signals for the signalId, making it distinguishable from the read tool.

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?

Explains what each action means and covers confirm/preview behavior, which gives clear usage context. It does not explicitly compare against other signal-related or approval tools, so it falls short of full alternative guidance.

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

All CrunchJunkie toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources