qidi-mcp

acquire_printer_lease

Claim exclusive printer access for your work so other agents are refused mutating actions; give a short reason and lease time, then renew for long jobs.

Instructions

Claim this printer for yourself, so other agents are refused mutating actions while you work. Give a short human reason ('bracket v3, ~40 min') — the point is that whoever gets blocked can see who to talk to. Refused if somebody else holds it. Expires on its own so a forgotten lease cannot strand the machine; renew it with renew_printer_lease for long jobs. This is cooperative: it does not stop the printer's own touchscreen or Fluidd.

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

Input Schema

Name	Required	Description	Default
`reason`	No
`confirm`	No
`minutes`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Nov 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing refusal-on-contention, self-expiry as a safety property, renewal as the extension path, and the important limitation that it is cooperative and does not block the touchscreen or Fluidd. That last point materially shapes what an agent can assume it has excluded.

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?

Front-loads the action and its effect in the first clause, then adds reason semantics, failure mode, lifetime, and scope caveat in tight succession. No filler sentences and nothing repeated from the schema.

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?

With an output schema present, return values need no explanation, and the description covers the mechanics an agent needs: contention, expiry, renewal, and cooperation limits. The unexplained `confirm` flag and the unspecified default/units behavior of `minutes` are the remaining gaps.

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 description coverage is 0%, so the description must carry the parameter meaning. It does well for `reason` (short human-facing text so blocked agents know who to contact) and hints at `minutes` via expiry/renewal talk, but `confirm` is never mentioned or explained, leaving one of three parameters opaque.

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 ("Claim this printer") plus the concrete effect ("other agents are refused mutating actions while you work"), which cleanly separates it from get_/renew_/release_/break_printer_lease siblings.

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?

Explicitly routes long jobs to renew_printer_lease and states the refusal condition when someone else holds the lease. It does not cover checking status first via get_printer_lease or resolving a stale lease via break_printer_lease, so alternative selection is clear but not exhaustive.

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

Deploy Server