Skip to main content
Glama

pms_jobs

Retrieve your personal list of unprinted library print jobs after SSO login to review pending print tasks before printing.

Instructions

图书馆自助文印个人未打印作业列表(需登录)。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does add two useful facts: the list is scoped to the caller's own jobs ('个人') and to jobs not yet printed ('未打印'), plus the login requirement. It says nothing about what happens when unauthenticated, whether the result is empty-safe, or how many entries come back. For a zero-parameter read tool that is an acceptable but thin account.

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 compact phrase with the resource, the implicit filter, and the auth condition, with the login caveat front-loaded in parentheses. Nothing is redundant. It is arguably too terse to be fully self-sufficient, but no sentence 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?

For a no-parameter read tool with no output schema, the description covers what is listed, whose jobs, and the login gate. It leaves the return shape and ordering unstated, which an agent would need to know before presenting results. Adequate for the tool's low complexity, but not complete.

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 no parameters, so there is no parameter meaning to add and the baseline applies. The description correctly implies the filtering is implicit (personal scope, unprinted only) rather than argument-driven, which prevents an agent from hunting for filter inputs.

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 resource and filter: the user's own unprinted print jobs at the library self-service printing service. The phrase '未打印作业列表' separates it from pms_print and pms_cancel, which act on jobs rather than list them, and from pms_stations, which lists hardware. It stops short of an explicit verb-plus-resource contrast with those siblings.

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 parenthetical '需登录' gives a real prerequisite, implying the tool is only usable in an authenticated session. There is no statement of when to prefer this over pms_stations, pms_print, or pms_cancel, and no exclusion such as whether printed jobs are excluded or how far back the list reaches. Usage is implied rather than specified.

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