Skip to main content
Glama

Make My QR Codes

List codes

list_codes
Read-onlyIdempotent

The account's codes, newest first: id, name, kind, what it holds or where it points, link, status and scans.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 50
folderNo
offsetNo
searchNoMatch in name, link ending or destination
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is fully covered elsewhere. The description adds genuinely new behavior — default ordering is newest first and each row carries a defined field set including derived data ("what it holds or where it points," "scans") — but says nothing about result volume, pagination, or what an empty result looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with no padding and the scope statement is front-loaded, which is good. The trade-off is under-specification rather than verbosity: it reads as a field inventory fragment without a leading verb, packing return fields where filtering guidance would be more actionable.

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?

With five parameters, 40% schema coverage and no output schema, the definition should carry more weight. Enumerating the returned fields usefully substitutes for the missing output schema, but an agent still cannot tell how to filter, how to page through results beyond the 100 max, or how this differs from get_code — significant gaps for a list tool with five optional filters.

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 only 40% (limit and search are documented; folder, offset and status are not), so the description is expected to compensate and does not. It mentions no filter, paging, or match semantics at all — not the default page size, not that search matches name/link-ending/destination, not the active/paused/blocked status filter — leaving three parameters with no explanation anywhere.

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

Purpose3/5

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

The description identifies the resource ("The account's codes") and implicitly a collection read, but the verb is elided into a noun phrase, so the agent has to infer "list" from the name/title. Naming the returned fields (id, name, kind, link, status, scans) does confirm it is a per-code summary listing, which broadly separates it from get_code, but the distinction is never stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: nothing says to call this to browse/enumerate versus get_code for a single record, or create_code/update_code for mutations. The only faint signal is "newest first," which implies an enumerating read but is not framed as usage guidance.

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