Skip to main content
Glama

AICTIONBOT™ Werkbank

Find comics from the KULIC Advisory Comic Library

find_comic
Read-onlyIdempotent

KULIC Advisory Comic Library: comics from twenty years of procurement and transformation practice, no clients and no figures. Three series: noir (book pages on ownership, ambiguity and the price of truth), transformation (shared services, sourcing and system roll-out journeys up to go-live, companies and systems invented or neutral) and german (four stories in German). Without a query it lists the whole library; with a query it returns the best matches by keywords in the titles (no AI). Each entry has the title, series, language of the comic, the image links of all versions and the page link. Show the images with KULIC Advisory as the source and the link to the library; sharing with a link is welcome, use in own documents after agreement. No sign-in, nothing stored.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of matches when a query is given. Default 6.
queryNoOptional keywords, for example 'ownership', 'go-live', 'GBS' or 'One Procurement'.
seriesNoOptional: only one series.
languageNoLanguage of the answer text. Default de. The comics themselves are in English or German.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly, non-destructive, idempotent, closed-world), the description discloses that no sign-in is needed, nothing is stored, results include all version image links and a page link, and it specifies attribution and sharing terms. This is unusually rich behavioral context.

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?

The description is a single dense paragraph, but every sentence contributes useful information (series breakdown, query behavior, output format, licensing). It could be more scannable with bullets, but it is not padded or repetitive.

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

Completeness5/5

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

Given the absence of an output schema, the description fully covers what each entry contains (title, series, comic language, image links, page link) and the terms of use. It also addresses safety (no sign-in, nothing stored) and search behavior, leaving little an agent would need to infer.

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 100%, so the baseline is 3, but the description adds meaning beyond the schema by clarifying that the query searches keywords in titles and that omitting it lists everything. It does not further explain limit, series, or language beyond the schema, but the query clarification is valuable.

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 names a specific resource (KULIC Advisory Comic Library) and what it contains (comics from procurement/transformation practice, three named series). An agent can immediately distinguish this from general search or other sibling tools by the unique comic-library scope.

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 clearly explains the core usage split: without a query it lists the whole library, with a query it returns keyword matches in titles (non-AI). It does not name alternative tools or explicitly say when to prefer this over a general search, but the contextual guidance is strong.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.