Skip to main content
Glama
Sign In
p21

p21

by mocchan0221
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Label format and design guide

p21_label_format
Read-only

Retrieve the P21 label JSON schema and design guidelines to structure label data correctly before designing, previewing, or printing labels.

Instructions

Get the P21 label JSON format (JSON Schema) and design guidelines. Call this first.

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_label_format"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/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 genuinely new context by stating the payload is a JSON Schema plus design guidelines, which matters since there is no output schema. Withholding only minor traits (e.g., whether the content is static or versioned) keeps it at 4.

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, zero waste, with the resource description front-loaded and the sequencing instruction last. Nothing could be removed without losing information.

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 parameterless, read-only reference tool the description is essentially complete: it says what is returned and when to call it. Only minor gaps remain, such as the size or structure of the guidelines payload, which a caller might want to anticipate.

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 the baseline is 4; there are no parameter semantics that the description needs to compensate for.

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 ('Get') and a specific resource ('P21 label JSON format (JSON Schema) and design guidelines'), which is clearly distinct from the action-oriented siblings (render, print, scan, save). It doesn't explicitly name how it differs from informational siblings like p21_fonts or p21_status, keeping it just below a 5.

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?

'Call this first' is an explicit, actionable ordering instruction that tells the agent when to invoke this relative to the other tools. There is no explicit when-not or named alternative, so it stops short of a 5.

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