Sora Commander

Overview Schema Source Related Servers Discussions Admin

list_folder_page

Page through a directory listing by path, offset, and limit when the initial listing is insufficient, without widening approved read roots. Read-only.

Instructions

Continue a bounded listing without widening Owner read roots.

Use to page a folder listing when list_folder's output is insufficient. Provide the same path, entry offset and limit. Read-only and confined to Owner read roots.

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": {
      "path": "<path>"
    },
    "name": "list_folder_page"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Same existing directory for next listing page; must remain inside approved roots.
`limit`	No	Maximum number of returned entries, 1 to 200; default 100.
`offset`	No	Entry offset for pagination, 0 to 10000; default 0.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Nov 9, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose two important traits: the operation is read-only and it is confined to 'Owner read roots' / 'approved roots'. It does not say what happens on an out-of-range offset, whether the response signals more pages, or how termination is indicated, which are the practical risks when paging.

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 no filler, and the operative instruction (use this when list_folder's output is insufficient) is front-loaded in the second sentence. The first sentence is slightly abstract but still earns its place by stating the safety scope.

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 simple three-parameter read tool with full schema coverage and an output schema present, the description covers purpose, the sibling alternative, reuse requirements, and the read-only/root-confinement profile. Nothing critical to invoking it correctly is missing.

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 100%, so the schema already documents path, limit, and offset with ranges and defaults. The description reinforces that these must match the prior call ('the same path, entry offset and limit'), a mild addition, but adds no format or semantics beyond the schema.

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 states a specific action ('continue a bounded listing', 'page a folder listing') on a specific resource (a folder), and explicitly identifies the sibling tool list_folder as the non-paged alternative. An agent can distinguish it from list_folder without opening either schema, though the opening clause emphasizes a constraint rather than the action itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Offers explicit when-to-use guidance: 'Use to page a folder listing when list_folder's output is insufficient,' naming the alternative and the condition that selects this tool. It also states what must be reused ('the same path, entry offset and limit'). It lacks explicit when-not guidance, such as behavior for the first page or after results are exhausted.

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