Skip to main content
Glama
Image Annotate MCP

Image Annotate MCP

by Thejiuyi

annotate_list

List saved image annotations from disk, newest first, so you can review human-marked boxes, points, and polygons before reloading or exporting them.

Instructions

List annotations saved on disk, newest first.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully states ordering (newest first) and storage source (on disk), which are real behavioral traits, but says nothing about what happens when no annotations exist, whether limit silently truncates, or the shape of returned items. For a low-risk read, this is acceptable but incomplete.

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 sentence with zero filler, front-loaded with the verb and resource, and the ordering qualifier placed where it is immediately useful. Nothing is redundant.

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 one-optional-parameter list tool with no output schema, the definition covers purpose and ordering but leaves the return contents and limit behavior undefined. An agent knows what to call but not what it will get back, which is a meaningful gap given no output schema exists to fill it.

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 `limit` parameter has default 20 and 0% schema description coverage, so the schema provides only a name and type. The description never mentions limit, paging, maximums, or what truncation looks like, so it fails to compensate for the coverage gap on the one parameter that governs output size.

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?

The description pairs a specific verb ("List") with a specific resource ("annotations") and adds scope ("saved on disk") plus ordering ("newest first"). It does not name a sibling to contrast with, but the siblings (cancel, export, load, render, wait) are operationally distinct enough that an agent can tell this is the read/enumerate path.

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?

There is no explicit when-to-use or when-not guidance, but "saved on disk" implicitly scopes the tool to persisted annotations rather than in-memory or rendered state. An agent must infer that this is the discovery step before annotate_load or annotate_render, which is a reasonable but unstated inference.

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