Skip to main content
Glama

QRavate QR codes

Options de design

list_design_options
Read-onlyIdempotent

Liste les styles prêts à porter, les icônes à placer au centre (Wi-Fi, menu, avis, PDF, vidéo…), les formes et les cadres utilisables dans le paramètre design des outils de création.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds the useful operational fact that this is a static catalog of allowed design values that feed a specific parameter elsewhere. It does not say whether the catalog is stable across calls or how large/structured the response is.

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?

A single well-formed sentence that front-loads the verb and then enumerates categories; the parenthetical examples of icons are informative rather than padding. The trailing clause about the design parameter is slightly buried but earns its place by giving the values a destination.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 carries the burden of describing return contents, and the enumeration does that at a category level. However, it never indicates the shape of returned values (identifiers vs. human-readable labels, nesting by category), which an agent needs to use the results programmatically in the design parameter.

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 the baseline of 4 applies. The mention of "le paramètre design" helpfully maps the returned values onto a field of a different tool, which is meaning beyond this tool's empty schema.

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?

Uses a specific verb ("Liste") plus an explicit enumeration of what is returned: ready-to-wear styles, center icons (Wi-Fi, menu, reviews, PDF, video), shapes and frames. It also names where the values belong (the design parameter of the creation tools), which separates it from generic listing siblings. It stops short of distinguishing itself by name from siblings like list_qr_codes, but the resource is unambiguous.

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 "utilisables dans le paramètre design des outils de création" implies the agent should consult this before setting a design, but it never states that explicitly nor names the tools that consume these values (create_qr_code, update_qr_design). There are no exclusions or when-not-to-use conditions, so usage must be inferred.

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