Skip to main content
Glama

Make My QR Codes

Code details and scans

get_code
Read-onlyIdempotent

One code's details, scan stats (per day, countries, devices; automated scans left out) and its recent changes.

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": {
      "code": "<code>"
    },
    "name": "get_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe code: its id from list_codes, or a changeable code's link ending (e.g. "menu" for makemyqrcodes.com/menu)
daysNoStats period, default 30

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the stats breakdown dimensions and the important caveat that automated scans are excluded, which materially affects how an agent interprets the numbers.

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 zero filler, packing the returned fields into a compact parenthetical. It is slightly dense as a noun phrase rather than a verb-led statement, but nothing needs to be cut.

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?

With no output schema, the description does the job of listing what comes back (details, stats, recent changes) and notes the automated-scan exclusion. Minor gaps remain — no indication of how many 'recent changes' are returned or how stats are bounded when days is omitted — but nothing critical for calling it correctly.

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 100%, with both 'code' (id or link ending, with example) and 'days' (enum, default 30) fully documented in the schema. The description adds no further parameter meaning, so the baseline 3 applies.

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 the specific resource ('One code's details') and enumerates the payload (scan stats per day/countries/devices, recent changes), so an agent knows this is a single-record fetch rather than a list. It does not explicitly contrast with list_codes, but the singular scope makes the distinction inferable.

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: fetch this when you need one code's details or stats. There is no explicit when-to-use/when-not guidance and no mention of alternatives such as list_codes for enumeration or update_code for mutations.

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