Skip to main content
Glama
Sign In
masscode-mcp

masscode-mcp

by MDizzleZA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

masscode_get_snippet

Retrieve a single snippet by ID, returning all its content fragments. Get complete snippet data directly from your massCode library.

Instructions

Get a single snippet by its ID, including all content fragments.

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": {
      "id": "<id>"
    },
    "name": "masscode_get_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSnippet ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden. It discloses that all content fragments are returned, but doesn't explicitly state read-only nature or error behavior. The word 'Get' implies non-destructive operation, but more context could be provided.

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, front-loaded sentence with no redundant words. It efficiently conveys the tool's purpose.

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?

For a simple getter with one parameter and no output schema, the description is reasonably complete: it specifies the resource and what is included. It lacks explicit mention of error handling or alternative tools, but the simplicity reduces the need for more.

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 schema already describes the id parameter fully (100% coverage), and the description only repeats 'by its ID' without adding further semantics. Baseline 3 is appropriate since the description doesn't enhance parameter understanding.

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 gets a single snippet by ID with all content fragments, using a specific verb and resource. It distinguishes itself from sibling tools like list_snippets and create_snippet by focusing on single retrieval.

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?

Usage is implied: use when you have a snippet ID and need the full snippet. However, it doesn't explicitly contrast with list_snippets or mention when not to use it, so guidance is limited to implication.

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