Lists the images of the Systra Tools media library (all AI-generated) with ready, permanently valid URLs to drop straight in. Optionally filtered by album and format, 100 per page.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page of the result, 100 images per page (optional, default 1). | |
| album | No | Album key to filter by (optional), e.g. 'natur', 'business', 'abstrakt'. Without one, every album is returned. | |
| format | No | Image format to filter by (optional). |
Changes observed during successful MCP inspections.
Input schema / properties / pageAdded value: +{
+ "description": "Page of the result, 100 images per page (optional, default 1).",
+ "minimum": 1,
+ "type": "integer"
+}Input schema / properties / album / descriptionPrevious value: -"Album-Schlüssel zum Filtern (optional), z. B. 'natur', 'business', 'abstrakt'. Ohne Angabe kommen alle Alben."New value: +"Album key to filter by (optional), e.g. 'natur', 'business', 'abstrakt'. Without one, every album is returned."Input schema / properties / format / descriptionPrevious value: -"Bildformat zum Filtern (optional)."New value: +"Image format to filter by (optional)."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It does disclose useful traits: the library is entirely AI-generated, URLs are 'ready, permanently valid', and results are paged at 100 per page. It omits ordering, stability guarantees, and any auth requirements, so the disclosure is partial.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences with zero filler; the primary capability ('lists the images... with ready, permanently valid URLs') is front-loaded and the filtering/paging detail follows. Every clause earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only, 3-parameter optional-filter list tool with no output schema or annotations, the description covers filtering, pagination, and the nature of the returned URLs. It is nearly complete, with only minor gaps around result ordering and authentication expectations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so page, album, and format are already fully documented with types, enum values, and defaults. The description only restates the album/format filters and page size, adding no syntax or semantics beyond the schema; baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Names a specific verb and resource (lists images of the Systra Tools media library), and adds distinguishing substance: all content is AI-generated and returns permanently valid URLs. It does not, however, explicitly differentiate itself from the sibling search_images, leaving the browse-vs-search distinction to inference.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The optional album/format filters imply a faceted browse use case ('Without one, every album is returned' appears in the schema, not the description), but there is no explicit when-to-use guidance or steering toward search_images when a query-based lookup is needed. Usage is implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.