Skip to main content
Glama

Illustration styles

show_styles
Read-onlyIdempotent

The illustration styles with an example picture of each, so the user can choose.

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": {
      "language": "<language>"
    },
    "name": "show_styles"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageYesTwo-letter code of the language the user writes in, e.g. 'en', 'nl', 'de'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and a closed world, so the safety profile is covered. The description adds that each style comes with an example picture, which is real return-value context since there is no output schema, but it does not say how pictures are delivered (URLs, identifiers) or how the language affects results.

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?

A single short sentence with no wasted words, and the key content (styles + example picture) is front-loaded. The phrasing is slightly noun-phrase-heavy rather than verb-led, but it stays efficient.

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-only listing tool with a fully documented schema, the definition is minimally sufficient. It omits how many styles exist, whether the list is stable/idempotent, and the form of the returned pictures, which matters more here because there is no output schema.

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 100% and the language parameter is fully documented with format and examples, so baseline is 3. The description adds nothing about what the language parameter actually changes (style names, example images, or both).

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 the resource (illustration styles) and what comes back with it (an example picture of each), plus the intent ('so the user can choose'). It lacks an explicit verb and does not differentiate itself from the sibling list_occasions, which also enumerates options, so it stops short of a 5.

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?

'So the user can choose' implies the usage context: present these options to the user for a selection step. However, no alternatives are named, no exclusions are given, and nothing states whether this must be called before a creation flow (e.g. create_book_plan).

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.

Resources