Skip to main content
Glama

update_caption

Fill in or correct the activity, command, and result caption for a saved screenshot so the log entry is accurate and complete.

Instructions

Fill in or fix the caption (activity, command, result) of a saved screenshot.

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

Input Schema

NameRequiredDescriptionDefault
fileYes
resultNo
commandNo
activityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose that this mutates an existing saved screenshot's caption rather than creating anything new, but it omits critical behavior: all three caption fields default to "" in the schema, so it is unclear whether omitting a field clears it or leaves it untouched, and nothing is said about permissions or what happens to an invalid file.

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 or redundancy. It is efficient, though its brevity is partly a symptom of under-specification rather than disciplined trimming.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter mutation tool with zero annotation coverage, no output schema, and 0% schema description coverage, the one-line description leaves major gaps: empty-default semantics, the identity meaning of "file", and any failure behavior. An agent could call it, but not confidently.

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% and there are 4 parameters, so the description must compensate. It only names the three caption components (activity, command, result) — essentially restating parameter titles — and never explains what "file" identifies, what format the caption strings take, or the consequence of the empty-string defaults.

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?

"Fill in or fix the caption (activity, command, result) of a saved screenshot" gives a specific verb (update/fix) and resource (caption on a saved screenshot), and the phrase "saved screenshot" implicitly separates it from capturing tools like save_screenshot. It does not explicitly name a sibling or exclusion, so it stops short of a 5.

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?

"Fill in or fix" hints at the use case: retroactively annotating an already-saved screenshot rather than creating one. However, there is no explicit when-to-use/when-not statement, no mention of prerequisites (does the screenshot need to exist?), and no pointer to an alternative tool for other annotation tasks.

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