Skip to main content
Glama
Sign In
drop2run-mcp

drop2run-mcp

Official
by Drop-to-run
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List folders

list_folders
Read-only

Lists the folder paths available on your account so you can set the correct folder when publishing. Create or rearrange folders in the dashboard; this tool only reads them.

Instructions

Lists the folders on this account, each with the path a publish's folder accepts. Folders are made and rearranged in the dashboard; no tool here creates one.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
foldersYesEvery folder on this account, ordered by path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.4

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely non-annotated context: folders are managed in the dashboard, so no create/rename/delete capability exists in this toolset and the returned set may change outside the agent's control.

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?

Two sentences, no filler. The core purpose and the per-item payload are front-loaded, and the dashboard/creation caveat follows as the secondary point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 shape need not be spelled out, yet the description still names the one field that matters downstream. Annotations carry the safety profile and there are no parameters to document — nothing an agent needs to call this correctly is missing.

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 and schema coverage is 100%, so there is nothing for the description to disambiguate. Baseline 4 applies for a zero-parameter read tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Lists the folders on this account') and then specifies what each returned item contains — the path that publish's `folder` parameter accepts. No sibling tool touches folders, so an agent can place this tool immediately.

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?

The description implies the use case by tying each folder to the `folder` argument of publish, and it explicitly closes off a dead end ('no tool here creates one' — created in the dashboard). It stops short of an explicit 'call this before publish_files to obtain a valid folder path' instruction.

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