Skip to main content
Glama

fetch_image

Retrieves an image file (PNG/JPG) from the GPU runtime and displays it inline for reviewing prediction visualizations, Grad-CAM, rollout frames, or saved figures.

Instructions

Fetch an image file (png/jpg) from the runtime and show it inline.

Use for prediction visualizations, Grad-CAM, rollout frames, or any figure your code saved to disk on the runtime.

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

Input Schema

NameRequiredDescriptionDefault
remote_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full load. It does disclose the key behavior that the image is shown inline and constrained to png/jpg from the runtime, but says nothing about failure modes (missing path, unsupported format, size limits) or how the image is returned.

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 short sentences, front-loaded with the action and resource, followed by a compact list of use cases. Nothing is redundant and there is no filler.

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 one-parameter read tool with no annotations and no output schema, the definition covers purpose and typical usage adequately. It stops short of describing edge cases, error behavior, or path resolution rules, which an agent would need when a fetch fails.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single remote_path parameter, so the description must compensate. It implies the path refers to a file saved to disk on the runtime, which is genuinely useful context, but it does not specify path format (absolute vs relative, working directory) or extension expectations beyond png/jpg.

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?

The description names a specific verb and resource (fetch an image file, png/jpg, from the runtime) and adds the distinctive behavior of rendering it inline. That separates it from a general file-download tool, though it never names a sibling to contrast with explicitly.

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?

It gives concrete triggering contexts: prediction visualizations, Grad-CAM, rollout frames, or any figure the code saved to disk on the runtime. What is missing is guidance on when not to use it (e.g., non-image files or files not on the runtime), which would have made this a 5.

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