Skip to main content
Glama

Get Library folder

get_library_folder
Read-onlyIdempotent

Lists visible direct children of a Library folder. Pass a folder ID or a Trainn folder URL. Results include child folders and visible Library items. Follow next_cursor for more entries.

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": {
      "folder": "<folder>"
    },
    "name": "get_library_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
folderYes
page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare a safe, read-only, idempotent, non-destructive, closed-world operation, so the description does not need to re-establish safety. It adds useful behavior by stating that only visible direct children are returned and that pagination continues via next_cursor, but it omits permission nuances and page-size behavior.

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?

The description is front-loaded and compact, with four sentences that each add useful detail. Minor repetition of “visible” is acceptable and does not impair clarity.

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?

For a read-only listing tool with no output schema, it describes the result composition and pagination adequately. It is slightly incomplete because page_size behavior and return structure details are not covered.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It explains that folder accepts an ID or URL and that cursor corresponds to next_cursor pagination, but it does not explain page_size or its 1-50 range, leaving one of three parameters undocumented.

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 uses a specific verb and resource: it lists visible direct children of a Library folder. That clearly separates it from broad folder listing or content search, though it does not explicitly name a sibling alternative.

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?

It explains how to invoke the tool by passing a folder ID or Trainn folder URL, but gives no guidance on when to use it instead of list_library_folders, search_library_content, or inspect_library_content. Usage is only implied by the purpose.

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.

Resources