Skip to main content
Glama
Sign In
lightbulb-mcp

lightbulb-mcp

by RPasquale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_folder

Browse documents in any folder of the document library to explore files and folder structures. Filter by source system and set maximum items.

Instructions

List documents in a folder or the entire document library.

Use this to browse the document library, see what files exist, and explore folder structures.

Args: folder_path: Folder path to list (default "/" for root) source_system: Filter by source (e.g. "google_drive", "microsoft_graph", "workspace") max_items: Max number of items to return (default 100)

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

Input Schema

NameRequiredDescriptionDefault
max_itemsNo
folder_pathNo/
source_systemNo

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?

With no annotations, the description carries full burden. It implies non-destructive read behavior but does not disclose details like pagination (despite having a 'max_items' parameter), error handling for invalid folders, or whether it returns only files vs. both files and folders. For a simple list operation, it is adequate but not comprehensive.

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?

The description is concise: a one-line summary, followed by contextual usage, then parameter details. Every sentence is necessary; no redundancy or verbosity.

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?

Given the presence of an output schema (not shown), return value details are not required. The description covers the basic purpose and parameter meanings. However, it lacks context on edge cases like folder not found or returned item structure (files vs. folders), which slightly reduces completeness for a list tool.

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?

Despite 0% schema description coverage, the description adds significant value by explaining each parameter: specified default paths, example source systems, and default max_items count. This compensates well for the lack of schema-level descriptions.

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 clearly states the action ('List documents') and resource ('folder or entire document library'), with examples like 'root'. However, it does not distinguish itself from sibling tool 'search_folder', which could be used for similar purposes but with different semantics.

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 description provides explicit usage guidance ('Use this to browse the document library, see what files exist, and explore folder structures'). It does not, however, indicate when to avoid this tool (e.g., for querying specific documents) or mention alternatives like 'search_folder'.

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

Deploy Server

Other Tools