Skip to main content
Glama
Sign In
masscode-mcp

masscode-mcp

by MDizzleZA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

masscode_list_snippets

List or search MassCode snippets, filtering by query, folder, or tag as needed.

Instructions

Search or list snippets from MassCode. Optionally filter by search query, folderId, or tagId.

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": "masscode_list_snippets"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagIdNoFilter by tag ID
searchNoFull-text search across snippet names and content
folderIdNoFilter by folder ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only mentions search/filter capability but does not state that this is a read-only operation, what the return format is, pagination behavior, or any side effects.

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 sentence that conveys the core purpose and optional filters with no redundancy. It is front-loaded and earns its place.

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?

For a simple list tool with low complexity and full schema coverage, this is a minimally viable description. However, it lacks explicit mention of return behavior or read-only nature, which would be expected for full completeness.

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 provides 100% parameter descriptions, so the baseline is 3. The description merely restates the optional filter parameters without adding extra syntax, defaults, or relationships beyond what the schema already covers.

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 action ('Search or list') and resource ('snippets from MassCode'), distinguishing it from sibling tools like masscode_get_snippet (single snippet) and folder/tag listing tools.

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 as a search/list tool with optional filters, but does not explicitly state when to prefer this over masscode_get_snippet or other alternatives. No exclusions or when-not-to-use guidance is provided.

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