Skip to main content
Glama
Sign In
p21

p21

by mocchan0221
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List saved templates

p21_list_templates
Read-only

Lists saved label templates with names, media, and variables, helping you select one for rendering or printing labels.

Instructions

List the user's saved label templates (name, media, {{variables}}). Use one with template in p21_render / p21_print.

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": "p21_list_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the useful fact that results include name, media and variables, which matters since there is no output schema. It says nothing about ordering, pagination, or behavior when the user has no saved templates, so it is a modest addition over the structured data rather than a rich one.

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?

Two short sentences, both front-loaded with the essentials: what is returned first, how to consume it second. No filler or restatement of the title.

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?

For a zero-parameter, read-only list tool with no output schema, listing the returned fields plus the render/print handoff covers what an agent needs to act. Minor gaps remain around ordering and empty-result behavior.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to explain at the input level; baseline 4 applies. The description correctly spends its words on the return shape instead of inventing input details.

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

Purpose5/5

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

States a specific verb (List) and a precise resource (the user's saved label templates), and enumerates what each entry contains (name, media, {{variables}}). That is enough to distinguish it from p21_save_template and from the single-label tools without opening a schema.

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

Usage Guidelines4/5

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

The second sentence gives concrete downstream guidance: take a returned template and pass it as `template` to p21_render or p21_print. It clearly implies 'call this first to discover templates', but it doesn't state any exclusions or when-not to use it (e.g. vs. p21_load_label).

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

Deploy Server

Other Tools