masscode-mcp

Overview Schema Source Related Servers Discussions Admin

masscode_create_snippet

Create a new code snippet in MassCode by providing a title and content, with optional tags, folder, and favorite status.

Instructions

Create a new snippet in MassCode.

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

Input Schema

Name	Required	Description
`name`	Yes	Snippet title
`tagIds`	No	Tag IDs to attach (numbers or strings)
`content`	Yes	One or more content fragments (tabs)
`folderId`	No	Parent folder ID (number or string)
`isFavorite`	No	Mark as favourite
`description`	No	Short description

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 17, 2026

TDQS

A3.5/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 the full burden. 'Create a new snippet' reveals that it performs a write operation but provides no additional behavioral context, such as idempotency, required permissions, response format, or side effects. This is a minimal level of disclosure, insufficient for a tool with no annotation support.

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, direct sentence. Every word is meaningful, and there is no redundancy or unnecessary elaboration. 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.

Completeness3/5

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

Given the 6 parameters and the nested 'content' structure, the schema provides thorough field-level guidance. However, the description lacks information about behavioral outcomes (e.g., return value, effects on tags/folders) and any usage conditions. It is minimally complete but leaves some gaps, especially since there is no output schema to clarify the response.

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?

Schema description coverage is 100%, with each property already having a clear description in the input schema. The tool description adds no parameter-level information, but since the schema is comprehensive, the baseline of 3 applies. The description does not need to repeat schema details.

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 specific action and resource: 'Create a new snippet in MassCode.' This distinguishes it from sibling tools like update_snippet, list_snippets, and create_tag/create_folder. The verb 'Create' and direct object 'snippet' make the purpose unambiguous.

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 implies usage context: you use this tool when creating a new snippet, as opposed to updating or retrieving one. However, it does not explicitly state when to choose this over alternatives, nor does it mention any prerequisites (e.g., existing folders or tags). This is adequate but leaves room for clarification.

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

Deploy Server