Skip to main content
Glama
ipp-bridge-mcp

ipp-bridge-mcp

List Uploaded Files

list_uploaded_files
Read-only

List non-expired files staged in the temporary upload store to identify documents available for IPP/CUPS printing, validation, job monitoring, or cancellation.

Instructions

List non-expired files currently staged in the temporary upload store.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

readOnlyHint=true already declares this is a safe, non-mutating operation. The description adds genuine context beyond that: expired files are filtered out of the result set, which is a behavioral fact the annotations do not convey. It stops short of describing ordering, result limits, or whether the store is per-session, which would matter for a staging-area listing.

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 front-loaded sentence with zero filler; the scope qualifier ('non-expired') appears before the resource description so the agent gets the key constraint first.

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-value details need not be restated, and with zero parameters the input side is trivially complete. The description covers the one non-obvious trait (expiry filtering); only minor items such as ordering or whether the staging store is scoped to the caller are unaddressed.

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 the schema carries no semantics to compensate for and the baseline is 4. The description correctly implies the full list is returned unfiltered by any caller-supplied argument.

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?

States a specific verb (List) and resource (files staged in the temporary upload store), and adds a meaningful scope qualifier, 'non-expired', that tells an agent exactly which files are returned. It does not name the sibling read/write tools (get_uploaded_file, delete_uploaded_file), so differentiation is inferred from the verb rather than stated.

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?

Usage is implied by the verb and scope: an agent can tell this is the enumeration step before calling get_uploaded_file or delete_uploaded_file. However, there is no explicit when-to-use or when-not-to-use statement, and no mention of whether this is the required discovery step prior to those sibling operations.

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