Skip to main content
Glama
@elido/mcp-server

@elido/mcp-server

Official
by elidoapp

generate_qr

Create QR codes for existing short-link slugs and return an artifact URL plus PNG or SVG bytes for small sizes.

Instructions

Generate a QR code for an existing link slug. Returns the artifact URL plus PNG/SVG bytes when small.

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": {
      "link_id": "<link_id>"
    },
    "name": "generate_qr"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
formatNosvg
link_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the return shape (artifact URL plus PNG/SVG bytes) and a conditional caveat ('when small'). It omits what happens for large outputs (URL only?), whether an artifact is regenerated or cached per call, and whether any permissions or side effects apply.

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 compact sentences, front-loaded with the action and followed by the return behavior. No filler, though the 'slug' wording introduces a small inconsistency worth resolving.

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?

There is no output schema, so the return-value sentence is valuable and covers the essentials. Against a 3-parameter, annotation-free generation tool, however, the definition leaves parameter meaning and side-effect/caching behavior unexplained.

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 explain all three parameters and does not. It hints at the format parameter via 'PNG/SVG' and at size via 'when small', but never explains that size is a pixel dimension with a 64–2048 range and a 512 default, nor clarifies that link_id is a numeric identifier rather than a slug string.

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 ('Generate a QR code') and scopes it to an existing link. The scope phrase 'existing link slug' is slightly at odds with the actual required parameter 'link_id' (integer), a small ambiguity, but the core action is unmistakable and distinct from siblings like create_link or query_analytics.

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 phrase 'for an existing link slug' implies the precondition that a link must already exist, which is useful implied guidance. It never states when to prefer this over other tools, what to do if the link does not exist (e.g., call create_link first), or any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.