Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

stop_watching_changes

Idempotent

Detach the active change listener to stop live Aseprite canvas update notifications. Use it when monitoring edits or QA checks is no longer needed.

Instructions

Detach the watch_changes listener.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already provide idempotentHint=true, so the agent knows repeated calls are safe. The description adds the key linkage to watch_changes but says nothing about side effects such as discarding pending change notifications, erroring when nothing is being watched, or whether the change log remains retrievable via get_watched_changes.

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?

A single short sentence with the object of the action front and center, and zero redundant wording. Nothing could be removed without losing meaning.

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 zero-parameter teardown tool with an idempotency annotation and no output schema, the description supplies what is needed to call it correctly. Only minor post-call behavior (what happens to buffered changes) is left implicit, which is acceptable at this complexity.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. No parameter guidance is missing.

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 a specific verb ("Detach") and names the exact resource/relationship it tears down (the ``watch_changes`` listener), which lets an agent pair it with the watch_changes sibling. It stops short of describing what the tool actually stops receiving, but the intent is unambiguous.

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 only implied: an agent can infer it should call this to end a previously started watch_changes session. There is no explicit statement of when to call it, whether it is required before re-watching, or what happens if no listener is active.

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