Skip to main content
Glama
JackXuyi

Current operating environment

getPrinterInfo

Retrieve printer details from your current operating environment to identify available devices and their configurations.

Instructions

获取当前设备的打印机信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for getPrinterInfo tool that retrieves printer information using systeminformation library's printer() method and returns it as JSON.
    case "getPrinterInfo": {
      const printerInfo = await si.printer();
      return {
        content: [{
          type: "text",
          text: JSON.stringify(printerInfo, null, 2)
        }]
      };
    }
  • src/index.ts:244-252 (registration)
    Registration of the getPrinterInfo tool in the listTools response, including name, description, and empty input schema.
    {
      name: "getPrinterInfo",
      description: "获取当前设备的打印机信息",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • Input schema for getPrinterInfo tool, which requires no parameters.
    inputSchema: {
      type: "object",
      properties: {},
      required: []
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it 'gets' information, implying a read-only operation, but doesn't disclose behavioral traits like whether it requires permissions, what format the output is in, or if it might fail if no printer is available. This leaves significant gaps for a tool with no annotation coverage.

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?

The description is a single, efficient sentence in Chinese that directly states the tool's purpose without any unnecessary words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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

Completeness2/5

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

Given the complexity of a hardware query tool with no annotations and no output schema, the description is incomplete. It doesn't explain what information is returned (e.g., printer name, status, capabilities) or potential errors, leaving the agent with insufficient context for reliable use.

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 has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add or detract from parameter semantics, but with no parameters, a baseline score of 4 is appropriate as there's nothing to compensate for.

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 clearly states the verb '获取' (get) and resource '打印机信息' (printer information) with scope '当前设备的' (current device's), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'getGraphicsInfo' or 'getHardwareInfo' that might also provide hardware-related information.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, such as whether the device must have a printer connected, or exclusions like when other tools might be more appropriate for related hardware queries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JackXuyi/env-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server