Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

get_watched_changes

Read-only

Retrieve the change count recorded since change watching began, with an option to reset the counter to zero after reading.

Instructions

Poll the change counter started by watch_changes (reset=True zeroes it after reading).

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

Input Schema

NameRequiredDescriptionDefault
resetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the important extra context: this reads a counter that another tool started, and reset=True zeroes it after reading — a state side effect the agent must know about. That disclosure is exactly the value-add the annotations lack, though the tension between a state-zeroing option and readOnlyHint=true is left for the caller to reconcile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One compact sentence with the tool's dependency and the parameter caveat front-loaded; no filler. The RST-style double backticks are slightly noisy but do not harm comprehension.

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?

There is no output schema, so the description should say what a 'change counter' returns (a count, a delta since last poll, changes since a point). It conveys the state machine but leaves the return value and polling semantics to inference.

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 description coverage is 0% for the single 'reset' parameter, but the description compensates by defining its effect ('zeroes it after reading'), which is more useful than a bare type/default. It does not say what happens when reset is false beyond the obvious read-only behavior.

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 (poll) and a specific resource (the change counter started by watch_changes), which cleanly separates it from watch_changes and stop_watching_changes. It stops short of explicitly naming the sibling alternatives, but the referenced lifecycle makes the role 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?

The prerequisite is implied strongly by 'started by watch_changes', so an agent can infer it must call watch_changes first. There is no explicit guidance on when to use this versus explain_changes or stop_watching_changes, nor on polling cadence or termination.

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