Skip to main content
Glama

QRavate QR codes

Afficher un QR code

get_qr_code
Read-onlyIdempotent

Détail d’un QR code, par identifiant ou code court, avec son image (aperçu, téléchargement PNG et SVG).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_qr_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description need not restate the safety profile. Even so, it adds useful return-surface information that no output schema provides: the response carries the QR code's images as a preview and as downloadable PNG and SVG files. Permissions and error behavior remain unstated.

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?

One short sentence front-loads the resource ('Détail d'un QR code'), then the lookup modes, then the returned assets. Nothing is repeated and no sentence is wasted.

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 single-parameter read tool with an annotation set that already covers safety and idempotency, the description covers what the tool returns, including the three image formats, which is the key gap because no output schema exists. Only the expected shape of the short code and the not-found behavior are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the single 'id' parameter is documented nowhere else; the description partially compensates by saying it accepts either a full identifier or a short code. It gives no format example, no case or length expectations, and no indication of what happens if the value is ambiguous or not found.

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?

The description names a specific resource and scope: retrieving the detail of one QR code plus its rendered images. It is clearly a read tool, which contrasts with the mutation-oriented siblings like create_qr_code and rename_qr_code. It does not explicitly differentiate itself from list_qr_codes, which prevents a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never states when to use this tool instead of list_qr_codes, get_stats, or export_qr_codes, and it gives no prerequisites or exclusions. The lookup requirement is only implied by the phrase 'par identifiant ou code court'. It offers no routing guidance.

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