Skip to main content
Glama

Ready-made styles

list_presets
Read-only

Lists genframe «Готовые промты» presets: turn a person's photo into a stylised avatar (e.g. crime-game poster, spy film poster). Each has several scenes (styles). Free.

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_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: presets are free, each contains multiple scenes/styles, and they produce avatar-style output (crime-game poster, spy film poster). It stops short of describing the exact shape of returned items, which matters somewhat with no output schema.

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?

Three short sentences, front-loaded with the core action, then definition, then structure and cost. Every sentence carries information; the only mild friction is the mixed Russian product name, which is harmless but not self-explanatory.

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 zero-param listing tool with annotations covering safety, the description supplies what an agent needs: what presets are, that each holds several scenes, and that they cost nothing. Minor gap: with no output schema, the description does not say what fields each preset record exposes (id, name, scene list), which would help an agent chain into generate_preset.

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?

The tool takes zero parameters, so there is nothing for the description to clarify; the schema is trivially complete at 100% coverage. Baseline for a no-parameter tool applies, with no parameter-level meaning to add.

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 and resource ("Lists ... presets") and explains what a preset is: a ready-made style that turns a photo into a stylised avatar, with examples. This clearly separates it from list_generations/list_models, though it never explicitly contrasts itself with the sibling generate_preset.

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: describing presets as ready-made avatar styles with several scenes suggests the browse-then-generate workflow, and the "Free" note hints at costless exploration. There is no explicit when-to-use statement, no mention of generate_preset as the follow-up action, and no exclusions.

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