Skip to main content
Glama

QRavate QR codes

Lister les QR codes

list_qr_codes
Read-onlyIdempotent

Liste les QR codes dynamiques de l’espace, avec recherche par nom ou destination.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
stateNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds one genuinely useful behavioral fact — that only dynamic QR codes in the workspace are returned — but says nothing about ordering, default page size, or pagination beyond the schema's limit cap.

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 front-loaded sentence with no filler or redundancy. It is efficiently sized, though the scope qualifier and search note are compressed into one clause rather than structured for quick scanning.

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?

A read-only filtered list with three optional parameters and annotations covering its safety profile is a modest tool, and the description covers scope and search. It still omits what a caller likely needs — default result count, ordering, and how static QR codes are listed (a sibling create_static_qr_code exists) — and with no output schema, return contents go unmentioned.

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 description must carry parameter meaning; it clarifies that `search` matches on name or destination, which is real added value. However, `limit` and `state` (active/paused/blocked) are never explained beyond their raw schema types, so coverage remains partial.

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 and resource ("Liste les QR codes dynamiques de l’espace") plus the built-in search capability, which clearly separates it from get_qr_code and create_qr_code. It does not explicitly name a sibling it is not (e.g. export_qr_codes), so it stops short of full differentiation.

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 listing intent is implied by "Liste", but there is no explicit statement of when to use this versus export_qr_codes (bulk export) or get_qr_code (single record). No prerequisites or exclusions are given, leaving the agent to infer routing.

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