Skip to main content
Glama
Sign In
stashcat-api-mcp

stashcat-api-mcp

by dclausen01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_folder

Create folders in Stashcat to organize files across channels, conversations, and personal storage by specifying name, parent folder, and storage type.

Instructions

Creates a new folder in a storage area.

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": {
      "name": "<name>",
      "parent_id": "<parent_id>",
      "type": "<type>",
      "type_id": "<type_id>"
    },
    "name": "create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFolder name
typeYesTarget storage type
type_idYesChannel, conversation, or user ID
parent_idYesParent folder ID (use "0" for root)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility. It confirms the action is a create (write operation) but does not disclose permissions, idempotency, behavior on duplicate names, or what the response contains.

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 a single, clear sentence with no redundant information. It is appropriately concise and front-loaded.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create operation with no output schema and no annotations, the description is too sparse. It does not explain the relationship between type and type_id, the meaning of parent_id '0', or the expected success/error behavior, leaving the agent under-informed.

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?

The input schema fully documents all 4 parameters with descriptions and an enum for 'type'. The description adds no extra semantic value beyond the schema, so a baseline of 3 is appropriate.

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 the tool's function with a specific verb ('creates') and resource ('a new folder in a storage area'). It is distinct from sibling tools like delete_folder, and the resource type is unambiguous.

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?

No guidance is provided about when to use this tool vs alternatives. It does not mention prerequisites, such as needing an existing parent folder, or when to choose this over other storage operations.

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