Skip to main content
Glama

List QR styles

list_qr_styles
Read-onlyIdempotent

List the body patterns, corner eye shapes, eye dot shapes, the frames (built-in styles and those drawn as templates), error correction levels, defaults and limits accepted by generate_qr_code and the image API.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description correctly spends its words on content scope instead. It usefully discloses that frames include both built-in styles and those drawn as templates, and that defaults and limits are included, which is more than the annotations convey.

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?

One front-loaded sentence beginning with the verb, with every clause naming a distinct category of returned data. It is dense but not padded; only the parenthetical about frames costs a little readability.

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 parameterless, read-only enumeration with no output schema, the description covers the important ground by naming the categories of values returned. It is slightly thin on response shape (e.g., whether results are grouped per category or returned in a single object), which is the only real gap.

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, so there is no parameter meaning to add and the baseline is 4. The description does not waste space restating an empty parameter set.

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?

"List" plus a concrete enumeration of what is listed (body patterns, eye shapes, frames, error correction levels, defaults, limits) makes the purpose unmistakable. It also ties the output to generate_qr_code, though it never distinguishes itself from the sibling list_options, so a 5 is not warranted.

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 phrase "accepted by generate_qr_code and the image API" implies the tool is a lookup to run before generating a code, but that is inference rather than an explicit when-to-use statement. No when-not conditions and no comparison to alternatives such as list_options are given.

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.