Skip to main content
Glama

List Library files

list_library_files
Read-onlyIdempotent

Files saved in the person's FynePDF Library, newest first (pinned on top). Pass an id as library_file_id to any tool.

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_library_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoPart of a file name.

Output Schema

NameRequiredDescriptionDefault
filesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / files / items / properties / pages / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / files / items / properties / pages / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavior beyond them: the result ordering (newest first, with pinned items hoisted to the top) and the fact that returned ids are portable across other tools. Neither is derivable from the annotations or the input schema.

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?

Two short sentences with the resource and ordering front-loaded and no padding. It is arguably too terse for a tool with undocumented filters, but nothing written 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?

An output schema exists and annotations are rich, so return values and safety do not need explaining. Still, for a listing tool with a search filter and a near-identical sibling, the description leaves the list_files-vs-list_library_files decision and the limit parameter unaddressed, which is a real completeness gap.

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 only 50%: 'query' is documented as 'Part of a file name' but 'limit' has no description at all, and the description does not compensate for that gap. Worse, the only identifier it highlights, library_file_id, is not a parameter of this tool, so it adds no calling semantics for the two parameters that actually exist.

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 the specific resource (files in the person's FynePDF Library) and its ordering (newest first, pinned on top), which lets an agent recognize the result set immediately. However, it omits an explicit verb and never distinguishes itself from the sibling tool list_files, so the agent must infer which listing endpoint to pick.

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?

There is no guidance on when to use this instead of list_files, nor any mention of the query/limit filters. The one routing hint present — 'Pass an id as library_file_id to any tool' — usefully tells the agent what to do with returned items, but that is downstream usage rather than when-to-call guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.