Skip to main content
Glama
context-attachment-manager

context-attachment-manager

View omitted images

cam_view_image
Read-only

Retrieves the original version of omitted images by ID so you can inspect full visual content when placeholders or prior descriptions are insufficient.

Instructions

View the originals of one or more omitted images in this task. Omitted images appear in the conversation as "[Image IMG-xxx omitted…]". Call it only when an answer needs to look at an image and what you said about it before is not enough; the originals are included only in this turn.

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

Input Schema

NameRequiredDescriptionDefault
idsYesIds of the images to view, e.g. ["IMG-004"]; pass several at once if you need several.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely new behavior: the originals are surfaced only for this turn, which tells the agent the result is ephemeral and cannot be re-read later without another call — a non-obvious, decision-relevant trait.

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 tight sentences, front-loaded with the purpose, then the gating condition and the one-turn lifetime. Nothing is redundant or padded.

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

Completeness5/5

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

For a single-parameter, read-only tool with full schema coverage and no output schema, the description covers purpose, trigger condition, id format, and result lifetime. Nothing material is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema cannot: it ties the 'ids' values to the visible omission markers and confirms that multiple originals may be requested in one call, which is the key operational hint for constructing the array.

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?

States a specific verb and resource ('View the originals of one or more omitted images') and even names the placeholder token ('[Image IMG-xxx omitted…]') the tool acts on, so an agent can connect the tool to what it saw in the conversation. No siblings exist, so differentiation is not required.

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 an explicit trigger ('only when an answer needs to look at an image') and an explicit exclusion ('what you said about it before is not enough'), which discourages needless re-fetching. No alternatives are named, but none appear to exist.

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

Deploy Server

Other Tools