Skip to main content
Glama

VHS Label Maker — texs.org

Describe a format

describe_format
Read-only

One format in detail: the printed sheet in px and inches at export DPI, every panel (front, spine, back, flaps…) as a rectangle with its pixel size, and which intent sections the format accepts. Call this BEFORE generating artwork for a format so each image is made at the right size and aspect.

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": {
      "format": "<format>"
    },
    "name": "describe_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatYesA slug from list_formats

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / format / enum
      Previous value: -[
      -  "slipcover",
      -  "side-load-vhs",
      -  "doublevhs",
      -  "betamax",
      -  "compact-tape",
      -  "bluray-cover",
      -  "bluray-slipcover",
      -  "dvd-cover",
      -  "steelcase",
      -  "clamshell",
      -  "polycase",
      -  "cardbox",
      -  "disc",
      -  "cassette",
      -  "cassingle",
      -  "jcard",
      -  "cd",
      -  "cd-tray",
      -  "cd-insert",
      -  "vinyl-label",
      -  "vinyl-jacket",
      -  "vinyl-sleeve",
      -  "minidisc-label",
      -  "minidisc-full-labels",
      -  "minidisc-jcard",
      -  "minidisc-cover",
      -  "minidisc-tray"
      -]New value: +[
      +  "slipcover",
      +  "side-load-vhs",
      +  "doublevhs",
      +  "betamax",
      +  "compact-tape",
      +  "bluray-cover",
      +  "bluray-slipcover",
      +  "dvd-cover",
      +  "steelcase",
      +  "clamshell",
      +  "polycase",
      +  "cardbox",
      +  "vhslabels",
      +  "betamax-labels",
      +  "disc",
      +  "cassette",
      +  "cassingle",
      +  "jcard",
      +  "cd",
      +  "cd-tray",
      +  "cd-insert",
      +  "vinyl-label",
      +  "vinyl-jacket",
      +  "vinyl-sleeve",
      +  "minidisc-label",
      +  "minidisc-full-labels",
      +  "minidisc-jcard",
      +  "minidisc-cover",
      +  "minidisc-tray",
      +  "obi-strip"
      +]
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds substantive context by disclosing the shape of the return payload (sheet size, panel rectangles, accepted intents) even though no output schema exists. It does not discuss error behavior for an invalid slug or whether results are stable across DPI settings, which keeps it below a 5.

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 sentences, zero filler, and the payload contents are front-loaded ahead of the usage rule. The parenthetical '(front, spine, back, flaps…)' earns its place by making 'panel' concrete without expanding length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the burden of explaining return values and does so thoroughly for a single-parameter read tool. Nothing an agent needs in order to decide to call it and to interpret the response is missing.

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 coverage is 100% and the enum lists all 30 slugs, so the structured fields already carry the parameter semantics. The description explains what the format drives downstream (panels, sizes, intents) but adds no per-argument meaning beyond what the schema provides, so the baseline 3 applies.

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?

The description names the specific verb+resource (describe one format in detail) and enumerates exactly what comes back: printed sheet dimensions in px and inches at export DPI, per-panel rectangles with pixel sizes, and accepted intent sections. That level of specificity clearly separates it from list_formats (catalog) and from compose_design/export_design (which act on artwork).

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?

It gives explicit ordering guidance and the reason for it: 'Call this BEFORE generating artwork for a format so each image is made at the right size and aspect.' That covers when to use it well, but it never states an exclusion or names the sibling to use instead for the format catalog (list_formats only appears in the schema's param description).

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