Skip to main content
Glama

List design options

list_options
Read-onlyIdempotent

List every value design_qr accepts: content types with their fields, colors and gradients, body patterns, eye and eye center shapes, frame styles and their text limit, custom frames, QRdx's official frames by id (holidays, seasons and uses), the frames drawn as templates, logo icons, built-in presets, error correction levels, margin and size limits, and how the scan score works.

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

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 cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description only needs to add context. It does so usefully by disclosing the breadth of the catalog returned, including non-obvious entries like custom frames, template-drawn frames, and an explanation of how the scan score works. Absence of any pagination or response-shape note is a minor gap for a full-catalog read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the key constraint in the first clause, which is good. But the remainder is a single sprawling comma-spliced list of a dozen categories, which is harder to scan than a short structured enumeration and mixes return-value detail into the purpose sentence.

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?

With no output schema, the description carries the burden of telling the agent what comes back, and it largely succeeds by enumerating the categories (colors, gradients, patterns, frames, presets, error correction levels, limits, score explanation). It does not describe the response structure or field naming, which would help an agent consume the result without trial and error.

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 takes zero parameters, and the description correctly spends no words on input semantics. Baseline for a no-parameter tool is 4, and nothing in the text misleads about inputs.

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?

Opens with a specific verb and scope: "List every value design_qr accepts," which immediately ties the tool to its companion design tool. The enumeration that follows makes the resource concrete. It stops short of naming a sibling it should be preferred over (e.g. list_qr_styles), so differentiation is inferred rather than stated.

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?

The implied usage is clear from "every value design_qr accepts" — call this to discover valid inputs before invoking design_qr. However, no explicit when-to-use or when-not guidance is given, and the definition never contrasts itself with list_qr_styles, which an agent could plausibly confuse it with.

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.