Skip to main content
Glama
Sign In
uleszka

uleszka

by jokerwader
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Pokaż obraz

get_image
Read-only

Retrieve an archived image with its AI description by path, or list all images and descriptions for a given article ID to review visual content.

Instructions

Returns an image from the archive together with its AI description. Pass a path shown in read_article (e.g. zrodlo/webacja/01potop/gilgam.gif), or an article id to list that article's images with their AI descriptions.

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": "get_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoŚcieżka obrazu z treści artykułu
article_idNoZamiast ścieżki: id artykułu – zwraca listę jego obrazów z opisami

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4/5.0
Behavior3/5

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

readOnlyHint=true already covers safety, and the description adds the meaningful behavioral fact that both modes return AI descriptions and that article_id switches to list semantics. It does not disclose the image return format (binary/URL/base64), size limits, or whether the list mode is paginated.

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 sentences, front-loaded with the return behavior and then the parameter routing, with zero redundant wording.

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?

For a two-parameter read tool with no output schema, the description covers both modes and what comes back. Only the concrete output shape (image encoding, list pagination limits) is left unspecified.

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 coverage is 100%, so the schema already documents both parameters. The description adds a concrete path example and names read_article as the source of valid paths, which is modest added value beyond the Polish schema strings but does not explain path normalization or error behavior for bad paths.

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?

The description opens with a specific verb+resource ('Returns an image from the archive together with its AI description') and immediately distinguishes the two operating modes (single image by path vs. list by article id), which no sibling tool offers.

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 routes the agent explicitly: take a path that read_article showed you, or supply an article_id to enumerate that article's images. The conditional selection between the two parameters is spelled out, though there is no explicit exclusion about when not to call it.

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