Skip to main content
Glama

QRavate QR codes

Renommer un QR code

rename_qr_code
Idempotent

Change le nom d’un QR code, celui qui sert à s’y retrouver dans l’espace et les statistiques. Le code imprimé et sa destination ne changent pas. Nécessite l’accès en écriture.

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": {
      "qr": "<qr>",
      "name": "<name>"
    },
    "name": "rename_qr_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
qrYes
nameYesNouveau nom, par exemple « Menu terrasse été ».

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (non-read-only, non-destructive, idempotent, closed-world), and the description adds genuinely new behavioral context: the write-permission requirement and the explicit blast radius — the printed code and its destination are untouched. It stops short of describing the response or what happens on an invalid/duplicate name.

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?

Three short sentences, no filler, with the core action stated first, the scope limitation second, and the permission requirement last. Every sentence carries distinct information.

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 simple two-parameter, idempotent, non-destructive rename with no output schema, the description covers what changes, what does not, and the access requirement. The only real omission is the expected form of the `qr` identifier, which is left entirely to the caller.

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 coverage is 50%: the `name` parameter already has a description and example in the schema, while `qr` is undocumented there. The description clarifies the semantic role of `name` (a human-facing label only, with no effect on delivery), but says nothing about what `qr` expects (ID vs. slug), so it only partially compensates for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ("Change le nom d’un QR code") and immediately scopes it: it is the label used to organize the workspace and statistics, not the printed code or its destination. That contrast with the printed code and destination lets an agent distinguish this from siblings like update_destination or update_qr_design without opening their schemas.

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 definition states a prerequisite ("Nécessite l’accès en écriture") and implies the boundary against destination-editing tools by saying the destination does not change. However, it never names an alternative or gives an explicit when-to-use versus when-not-to-use rule, so routing still requires inference from the sibling list.

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