Skip to main content
Glama

QRavate QR codes

Changer la destination

update_destination
DestructiveIdempotent

Change la destination d’un QR code dynamique (effective en une minute environ). 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>",
      "destination": "<destination>"
    },
    "name": "update_destination"
  }
}

Input Schema

NameRequiredDescriptionDefault
qrYes
destinationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true), so the description only needs to add context. It does add real value by disclosing the ~1 minute propagation delay and the write-access requirement, which are not in the annotations. It says nothing about whether the previous destination is recoverable or what happens if the URI is invalid.

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?

A single compact sentence with the effect and the timing front-loaded ahead of the access requirement. No filler or redundant restatement of the tool name.

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 simple two-parameter mutation with no output schema, the description covers timing and auth but leaves the identifier format and failure/reversibility behavior unaddressed. With 0% schema coverage, those gaps are the ones an agent most needs filled before calling.

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% for both parameters, so the description must carry the burden and largely does not. It implies that 'destination' is a redirect target but never states that 'qr' is an identifier/code reference or that 'destination' must be a valid URI, nor any length or scheme constraints.

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 states a specific verb and resource ('Change la destination d'un QR code dynamique'), which pins down that this modifies the redirect target rather than the code's design or name. It does not explicitly contrast with siblings like schedule_destination_change or set_redirect_rules, so differentiation is implied by the tool name rather than stated.

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 implied via the 'QR code dynamique' restriction, which implicitly excludes static codes, and the note that write access is required. However, it never says when to prefer this over schedule_destination_change (deferred change) or set_redirect_rules, leaving the agent to infer the boundary from names alone.

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