Skip to main content
Glama
Sign In
SuperSkill

SuperSkill

by permanu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

brainstorm

Destructive

Start or continue an idea document for a project by adding topic and content, with automatic project detection if omitted.

Instructions

Start or continue a brainstorm document for a project.

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": {
      "topic": "<topic>",
      "content": "<content>"
    },
    "name": "brainstorm"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesBrainstorm topic (used as filename)
contentYesContent to add
projectNoProject slug (auto-detected if omitted)
workspace_pathNoAbsolute thread workspace directory; must map to this project. Omit only when the server cwd is the thread workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.1
    • addedInput schema / properties / workspace_path
      Added value: +{
+  "description": "Absolute thread workspace directory; must map to this project. Omit only when the server cwd is the thread workspace.",
+  "type": "string"
+}
  2. First observedv0.6.1

TDQS

C2.9/5.0
Behavior2/5

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

The annotations declare destructiveHint=true, but the description does not disclose what is destructive: it never says whether 'start' overwrites an existing brainstorm document, where the file is written, or whether content is appended versus replaced. For a destructive-flagged write tool with no output schema, this is a meaningful gap.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity contributes to the under-specification noted elsewhere rather than being a virtue on its own.

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?

With four parameters, a destructive annotation, and no output schema, the description omits the file-writing behavior, overwrite semantics, and project auto-detection. An agent cannot fully predict the side effects of calling it.

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%, so the schema already documents all four parameters (topic as filename, content, auto-detected project slug, workspace_path constraint). The description adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (start/continue) and resource (brainstorm document) scoped to a project, so an agent can tell it apart from generic siblings like 'write' or 'template'. However, it does not explicitly differentiate itself from those siblings, which keeps it below a 5.

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?

There is no guidance on when to use this tool versus siblings such as 'write', 'template', or 'capture', and no exclusions or prerequisites. The implied usage (capturing brainstorming) is left entirely to inference.

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