Skip to main content
Glama

QRavate QR codes

Pause ou réactivation

set_qr_state
DestructiveIdempotent

Met en pause ou réactive un QR code. 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>",
      "state": "<state>"
    },
    "name": "set_qr_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
qrYes
stateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The description adds one genuinely useful behavioral fact beyond the annotations: write access is required. However, annotations already flag destructiveHint=true and idempotentHint=true, and the description never explains what 'paused' actually does to scans, whether existing scans fail or show a message, or whether the change is reversible — significant gaps for a destructive-flagged mutation.

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?

Two short sentences with the action front-loaded and no filler. It is efficient, though the terseness edges toward under-specification rather than pure conciseness.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive-flagged mutation with zero parameter documentation and no output schema, the description leaves too much open: the identifier format for 'qr', the effect of pausing on live scans, and the response are all unstated. The write-access note is the only real addition.

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

Parameters2/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 the burden, and it says nothing about either parameter. The 'state' enum (active/paused) is self-documenting in the schema, but 'qr' is completely unexplained — it is unclear whether it expects an ID, a short code, or a URL.

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 verb pair (pause/reactivate) and the exact resource (a QR code), which cleanly separates it from siblings like create_qr_code, rename_qr_code, or update_qr_design. It stops short of naming an alternative tool, but the operation 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?

Usage is only implied by the verb: an agent can infer it should call this when it wants to stop or resume a QR code. There is no explicit when-to-use vs. when-not guidance, no mention of prerequisites beyond write access, and no pointer to related tools for changing destinations or designs.

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