Skip to main content
Glama
Image Annotate MCP

Image Annotate MCP

by Thejiuyi

annotate_cancel

Close an annotation session and its local web server, cancelling any blocked waits so agents stop hanging and can continue.

Instructions

Close a session and its local web server. Anyone blocked in annotate_wait wakes up as cancelled.

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": {
      "session": "<session>"
    },
    "name": "annotate_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose two non-obvious effects: the local web server is shut down alongside the session, and pending annotate_wait calls return a cancelled outcome. It does not say whether the call is idempotent, what happens if the session is unknown, or what the response contains, which keeps it short of a 5.

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 sentences, no filler, and the primary action is front-loaded before the side-effect detail about annotate_wait. Every sentence contributes distinct information.

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?

For a simple one-parameter teardown tool with no output schema, the description covers the important destructive side effects well. However, the undefined 'session' argument and the absence of any error or idempotency behavior leave a meaningful gap for a call that shuts down a server.

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?

The single required parameter 'session' has 0% schema description coverage, and the description never explains what a session identifier is, its format, or where to obtain it (presumably from annotate_load or annotate_list). The word 'session' is used but its meaning as a parameter is left entirely to inference.

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?

The description states a specific verb and resource — 'Close a session and its local web server' — and goes beyond the name by naming the exact resources torn down. It also distinguishes itself behaviorally from the sibling annotate_wait by describing the effect on blocked calls.

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 rather than stated: mentioning that blocked annotate_wait calls wake up as cancelled hints at when this tool is relevant, but there is no explicit 'call this when finished' guidance or any statement of when not to call it (e.g., an already-closed session).

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