Skip to main content
Glama
Sign In
display-image-mcp

display-image-mcp

by frizzy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_images

Retrieve stored display images for all profiles or one profile, with URL, sha256, size, and last-changed time, to choose or monitor assets for e-paper, OLED, or TFT rendering.

Instructions

List stored images (all profiles, or one) with URL, sha256, size and last-changed time.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 load; 'List stored images' implies a non-destructive read, which is useful. It discloses the returned attributes but says nothing about ordering, pagination, or limits for a potentially large collection.

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?

One sentence, front-loaded with the verb and resource, containing the scope and return fields with no filler.

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

Completeness4/5

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

An output schema exists, so the field list need not be the description's job, and with one optional parameter the surface area is small. Ordering and volume behavior are the only real gaps.

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 0% for the single 'profile' parameter, so the description must compensate. '(all profiles, or one)' explains that omitting or nulling the parameter returns everything, which the schema's bare anyOf/string/null does not convey; only the expected identifier format is left unspecified.

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 (List) and resource (stored images), and adds scope (all profiles, or one) plus the returned fields. An agent can separate it from render_image and delete_image, though no sibling is named explicitly.

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 only implied: the tool exists to enumerate images, and the parenthetical hints at the optional profile filter. There is no statement of when to prefer this over render_image or list_profiles, and no prerequisites are given.

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