Skip to main content
Glama
Sign In
masscode-mcp

masscode-mcp

by MDizzleZA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

masscode_create_folder

Create a new folder to organize code snippets, with optional nesting under a parent folder.

Instructions

Create a new snippet folder.

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>"
    },
    "name": "masscode_create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFolder name
parentIdNoParent folder ID for nesting

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?

With no annotations provided, the description carries the full burden for behavioral transparency. It merely states the creation action without disclosing side effects, permissions, or response behavior. No details about nesting or error conditions are mentioned.

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?

The description is a single, concise sentence that immediately conveys the purpose without any fluff. However, it lacks additional context that could enhance usefulness, making it appropriately brief but not exemplary.

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

Completeness3/5

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

The tool is simple and the schema documents parameters well, but the description omits guidance on usage context and return behavior. For a create operation with no output schema, this is a minor gap, so the description is adequate but not fully complete.

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 already provides descriptions for both parameters (name: 'Folder name', parentId: 'Parent folder ID for nesting'). The tool description adds no additional parameter meaning, so the baseline of 3 applies.

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 'Create a new snippet folder' uses a specific verb (Create) and resource (snippet folder), clearly distinguishing it from sibling tools like create_tag and create_snippet. It unambiguously states what the tool does.

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?

The description gives no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It only describes the operation itself, leaving the agent without direction on selection.

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