Skip to main content
Glama
Sign In
Pretty Prompt MCP Server

Pretty Prompt MCP Server

by charliemday
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_library_folders

List folders in your Pretty Prompt library to get their UUIDs, with parent_id indicating nesting, before moving prompts.

Instructions

List folders in the user's Pretty Prompt library. Use this before move_prompt_to_folder to get folder UUIDs. Folders are a flat list; parent_id indicates nesting (null = root).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description supplies the behavioral context. It discloses that 'Folders are a flat list; parent_id indicates nesting (null = root),' which is a key structural detail that affects how callers interpret results. The read-only nature is implied by 'List,' though not explicitly stated.

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?

Three sentences deliver purpose, usage guidance, and a structural note without extraneous words. The description is front-loaded with the primary action.

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 zero-parameter input and no output schema, the description covers purpose, usage context, and a key data attribute. It is sufficiently complete for a simple folder-listing operation, though it could mention pagination or return shape.

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?

There are zero parameters in the schema, so the baseline score of 4 applies. The description adds no parameter details, which is appropriate since none exist.

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?

The description clearly states 'List folders in the user's Pretty Prompt library' with a specific verb and resource. It distinguishes itself from sibling tools by focusing on folders, and specifically mentions its role before move_prompt_to_folder.

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 explicitly instructs 'Use this before move_prompt_to_folder to get folder UUIDs,' providing a clear when-to-use scenario. It does not mention alternatives or exclusion cases, but the folder-specific scope is implicit.

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