Skip to main content
Glama
Sign In

QRdx

by io.github.bucharitesh
OverviewDiscussionsAdmin

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, border 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.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive behavior. The description adds useful context by naming the option families covered and mentioning that it explains scan scoring, making the scope of the read-only result clear.

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?

The description is a single front-loaded sentence organized as a catalog of supported option types. It is dense but not wasteful, since each listed category corresponds to a design_qr value family.

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?

With no parameters and no output schema, the description must explain the return contents, and it does so comprehensively by enumerating all option categories and the scan-score explanation. This is sufficient for a simple read-only discovery tool.

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?

This tool has zero parameters, so the baseline is 4. There is no parameter information to add, and the description appropriately focuses on the catalog contents instead.

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 ('List') and resource ('every value design_qr accepts'), then enumerates the option families. An agent can tell this is the discovery catalog for design_qr, though the description does not explicitly distinguish it from sibling list_qr_styles.

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 use case is implied: call this to discover valid values before invoking design_qr. However, there is no explicit when-to-use/when-not guidance and no mention of alternatives such as list_qr_styles or generate_qr_code.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All QRdx toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources