Skip to main content
Glama

Desk: Snooze or dismiss a signal

desk_signal_action

Snooze a signal tile for N days, dismiss it until its count grows, or clear every snooze - the same personal view state the desk's Snooze and Dismiss buttons write. Changes nothing on Amazon and nothing for other users.

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": {
      "action": "<action>"
    },
    "name": "desk_signal_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoSignal tile key (tile_key on a desk_decisions row, e.g. budget_caps, listing_issues, reorder, cogs_missing).
daysNosnooze only: 1-30 (default 3).
countNodismiss only: the count shown now; the tile returns when it grows past this.
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds genuinely useful scope beyond that: the write is personal view state only and 'Changes nothing on Amazon and nothing for other users', which bounds the blast radius. It does not cover return values or error cases, but the added context is meaningful for a mutation tool.

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 dense sentences, front-loaded with the actions and their meanings, followed by the effect scope. Every clause carries information; nothing is redundant or padded.

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 mutation tool with no output schema and 75% parameter coverage, the description supplies the essential context: the three modes, their parameter mappings, and the personal/no-side-effect scope. Missing only minor details like reversibility timing or a named sibling relationship.

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 75%, and the description adds meaning by tying each action to its parameter: 'for N days' (days), 'until its count grows' (count), and 'clear every snooze' (unsnooze_all). This clarifies how the enum values relate to the accompanying fields, going beyond the schema's own field descriptions.

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 specific verbs and resource: 'Snooze a signal tile', 'dismiss it', 'clear every snooze', mapping cleanly to the three enum actions. It also frames the tool as writing 'personal view state' the desk's buttons write, so an agent can distinguish it from data-reading siblings. It stops short of naming the closest sibling (desk_decisions) explicitly, so it is clear but not fully differentiated.

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 concrete context for each mode: snooze for N days, dismiss until the count grows, or clear every snooze, which tells an agent which action to pick in each situation. There are no explicit exclusions or named alternatives, but the mode-to-scenario mapping is clear.

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