Skip to main content
Glama
Image Annotate MCP

Image Annotate MCP

by Thejiuyi

annotate_load

Load a saved annotation by name or file path and return its full structured payload, including images, items, and template filenames for reuse.

Instructions

Load one saved annotation by name (or file path) and return the full structured payload: schema 2 with images[] -> items[] and template filenames.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the return payload shape ('schema 2 with images[] -> items[] and template filenames') and implies a read-only operation via 'load', but says nothing about behavior when the name is not found, whether a file path is read from disk, or any permission requirement.

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?

A single front-loaded sentence with no filler; the payload sketch is dense but informative. Only marginal cost is that the 'schema 2 with images[] -> items[]' fragment is terse enough to be ambiguous.

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?

Because there is no output schema, the description must convey the return shape, and it does so at a high level plus a structural sketch. For a load tool with no annotations, it still leaves error behavior and source-of-truth (server store vs. file path) unspecified.

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?

With 0% schema description coverage, the description must compensate for the single undocumented 'name' parameter, and it does: it clarifies that the value may be a name or alternatively a file path. That is meaningful added semantics beyond the bare string schema, though format or path conventions remain unstated.

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 and resource: 'Load one saved annotation by name (or file path)'. The word 'one' distinguishes it from a listing operation like annotate_list, though no sibling is named explicitly.

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: the singular 'one saved annotation' suggests retrieval when you already know the identifier, and the parenthetical 'or file path' hints at an alternate lookup route. There is no explicit when-to-use versus when-not, and no prerequisite such as first calling annotate_list to discover names.

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