Skip to main content
Glama
Sign In
Printer MCP

Printer MCP

by riniort
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Save a printer alias

set_printer_alias

Create or replace a short alias for an installed Windows printer to simplify selecting it in print requests.

Instructions

Creates or replaces a short alias for an installed Windows printer.

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": {
      "alias": "<alias>",
      "printer": "<printer>"
    },
    "name": "set_printer_alias"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasYes
printerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context by disclosing upsert semantics ('Creates or replaces'), which the annotations do not convey, but it says nothing about what happens to an existing alias beyond replacement, permission requirements, or error behavior.

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?

A single sentence, front-loaded with the operation and resource, with no filler. Nothing here needs trimming or reordering.

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?

For a simple two-parameter tool with annotations present and no output schema, the description covers the essentials minimally. It is adequate but leaves the 0%-documented parameters and the replace-overwrite behavior under-specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the entire burden for two parameters and mostly fails. 'Short alias' hints at the alias naming intent but omits the enforced pattern (^[a-zA-Z0-9_-]+$) and gives no guidance on how the printer argument is identified (name vs. queue).

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 specific verb pair ('Creates or replaces') and a precise resource ('a short alias for an installed Windows printer'), so an agent can distinguish it from set_path_alias, which targets paths rather than printers. It stops just short of explicitly contrasting the two siblings, so a 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus set_path_alias or set_print_profile, and no prerequisites or exclusions. The phrase 'for an installed Windows printer' only faintly implies a precondition that the printer must already exist.

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