Skip to main content
Glama
supvan-e11

supvan-e11

by marco308

release_printer

Disconnect the Bluetooth link so the phone app can connect to the label printer; the connection re-establishes automatically when needed.

Instructions

Drop the Bluetooth connection so the phone app can connect. The connection comes back by itself next time, and is also dropped after two idle minutes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that the release is non-destructive and self-healing ('comes back by itself next time') and reveals an automatic idle-timeout of two minutes. It does not say what happens if the connection is already down or what error states look like, though the output schema covers return values.

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 filler, and the action is front-loaded ahead of the rationale and the recovery behavior. Every clause carries information an agent needs.

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-argument tool with an output schema, the description covers purpose, motivation, reversibility, and an implicit timeout — enough to call it confidently. It could be marginally more complete by stating behavior when no connection exists, but nothing essential is missing.

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 disambiguate and the baseline of 4 applies. Schema coverage is complete and the description correctly adds no redundant parameter talk.

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 and resource ('Drop the Bluetooth connection') and immediately explains the intent ('so the phone app can connect'). This is unambiguously distinct from sibling operations like printer_status, feed_tape, and print_label, none of which release a connection.

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 clause 'so the phone app can connect' supplies a clear trigger condition for calling it. It stops short of naming what to do if the phone app is already connected or whether any prerequisite check (e.g. printer_status) should precede it, so alternatives are only implied.

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