Skip to main content
Glama

case_image_view

Returns a saved case image inline so a vision-capable MCP client can inspect visible objects and text for investigation.

Instructions

Return a saved image inline so a vision-capable MCP client can inspect it.

The model may describe visible objects and text, then save useful observations with case_note. Visual appearance alone cannot establish a person's identity.

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": {
      "case": "<case>",
      "image_id": "<image_id>"
    },
    "name": "case_image_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseYes
image_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/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 burden; it does disclose the return shape (image inline) and a real prerequisite (the client must be vision-capable), plus a caveat that visual appearance alone cannot establish identity. It omits how missing or invalid image references behave, any size/format constraints, and whether the image is scoped to the case.

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?

Three short sentences, front-loaded with the core action, with no redundancy. The identity caveat is slightly tangential to the invocation mechanics but is a legitimate warning for downstream reasoning.

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?

A simple two-required-parameter read tool with no output schema, so the return value is described adequately by 'inline'. Parameter semantics are left entirely unexplained, which keeps it from being complete.

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 both parameters rest entirely on their bare names 'case' and 'image_id'. The description adds no meaning about what a case identifier accepts or how image_id is obtained, which for a zero-coverage schema is a meaningful gap even though the names are suggestive.

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: return a saved image inline, with the intended consumer (a vision-capable MCP client) named explicitly. It does not differentiate itself from near siblings such as case_image_similar or image_analyze, so an agent still has to infer which read path to pick.

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 implied rather than stated: vision-capable clients can inspect the image, and the follow-on step of recording observations via case_note is named. There is no explicit when-not guidance or comparison to the other image tools (similar, crop, analyze, exif).

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