Skip to main content
Glama
supvan-e11

supvan-e11

by marco308

feed_tape

Advances tape one blank label at a time without printing, allowing you to position or separate labels on a SUPVAN E11 label maker.

Instructions

Feed the tape on by one label without printing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden. It reveals one useful trait — tape advances without marking — but says nothing about how much tape is consumed, whether the feed is reversible, what happens if tape is exhausted, or whether any printer state or authorization is required.

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 short sentence with no filler, and the non-printing behavior is front-loaded. The awkward word order ('on by one label') costs a little clarity but nothing is wasted.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the zero-parameter surface keeps the requirement low. However, for a physical actuator with no annotations, an agent still lacks information about feed quantity and failure conditions.

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 input schema has zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The only semantic ambiguity, feed amount, has no corresponding parameter to explain.

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 a concrete verb (feed) and resource (tape) and adds a distinguishing clause, 'without printing', which separates it from the print_label sibling. The garbled phrasing 'on by one label' slightly muddies whether it is a single-label or continuous feed, but the core purpose is recoverable.

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?

The 'without printing' phrase implies when this is preferred over print_label, but there is no explicit statement of when to use it versus preview or release operations, and no prerequisites (e.g., printer must be in a specific state). Usage is inferable rather than stated.

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