Skip to main content
Glama

Get available design options

get_design_options
Read-onlyIdempotent

List every design value Unplain accepts: the font catalog, the built-in theme presets and what each looks like, cover layouts, footer styles, the colour format, and the allowed range of every typography and spacing setting. Call this BEFORE styling an ebook so colours, fonts and sizes are chosen from what actually exists rather than guessed. An unrecognised font name or an out-of-range size is rejected and nothing is saved. Returns the same catalog for every account and needs no permissions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that the catalog is identical for every account, requires no permissions, and that invalid font names or out-of-range sizes are rejected with nothing saved. These are useful behavioral facts about validation, access, and determinism that the annotations alone do not provide.

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?

The description is front-loaded with the catalog contents, followed by timing guidance, validation behavior, and account/permission context. Every sentence contributes useful information and there is no noticeable filler.

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?

For a zero-parameter, read-only catalog tool with no output schema, the description is complete enough: it explains what is returned, when to call it, validation consequences, and that no permissions are needed. No important agent-facing context appears to be missing.

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?

The tool has zero parameters, so there are no inputs whose semantics need explanation; the schema already reflects the empty input object. The description adds useful context about what the tool returns, but parameter semantics are not applicable beyond the baseline.

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 uses a specific verb and resource: it lists every design value Unplain accepts, then enumerates the font catalog, theme presets, cover layouts, footer styles, colour format, and typography/spacing ranges. That scope is specific enough to distinguish this reference catalog from sibling tools like create_ebook, update_ebook, and list_brand_themes.

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 gives clear timing guidance: "Call this BEFORE styling an ebook" and explains why, so values are chosen from what exists rather than guessed. It does not explicitly name when not to use it or point to a sibling alternative, which keeps it below a 5.

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