Skip to main content
Glama
Image Annotate MCP

Image Annotate MCP

by Thejiuyi

annotate_render

Renders a saved annotation as a numbered image so agents can read the labels directly instead of asking users to type names. Requires a prior PNG export or renders on the fly.

Instructions

Render the numbered annotation picture for one saved annotation and return it as image content, so you can read the labels yourself instead of asking the user to type names. Needs annotate_export(fmt='png') to have been run first, or it will render on the fly.

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_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
image_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/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 load and does disclose the key traits: the output is image content rather than text, and there is a soft prerequisite that degrades to on-the-fly rendering. It omits cost/latency implications of that on-the-fly render and says nothing about failure behavior for an unknown name.

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, both front-loaded with the important information: what is produced and what it depends on. No filler or restatement of the tool name.

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 two-parameter render tool with no output schema, the description covers output type and prerequisites adequately. It falls short on the unexplained image_id parameter and on what happens when the named annotation does not exist.

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?

Schema description coverage is 0%, so the description must explain both parameters. It implicitly identifies 'name' as the saved annotation to render, but 'image_id' is never mentioned, leaving the caller to guess whether it selects an image, overrides one, or is optional context.

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 ('Render the numbered annotation picture for one saved annotation') and names the return type (image content), which separates it from annotate_export's file-producing role. It does not explicitly contrast with annotate_image, so sibling differentiation is only partial.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear motivating use case ('so you can read the labels yourself instead of asking the user to type names') and a dependency rule with fallback: annotate_export(fmt='png') should have run first, otherwise it renders on the fly. No explicit when-not-to-use case is given, which keeps it short of a 5.

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