Skip to main content
Glama
Sign In
copilot-mcp-server

copilot-mcp-server

by x51xxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

brainstorm

Solve creative challenges by generating ideas using structured frameworks, domain context, and feasibility analysis.

Instructions

Generate creative ideas using structured frameworks with domain context and feasibility analysis.

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

Input Schema

NameRequiredDescriptionDefault
modelNoAI model to use: 'gpt-5', 'claude-sonnet-4', 'claude-sonnet-4.5', or 'claude-haiku-4.5' (0.33x cost). Defaults to COPILOT_MODEL env var
addDirNoAdd directories to allowed list for file access
domainNoDomain: software, business, creative, research, product, marketing, etc.
promptYesBrainstorming challenge or question
ideaCountNoNumber of ideas (default: 12, range: 5-30)
workingDirNoWorking directory for command execution. Falls back to COPILOT_MCP_CWD env var or process.cwd()
constraintsNoLimitations: budget, time, technical, legal, etc.
methodologyNoFramework: divergent, convergent, scamper, design-thinking, lateral, auto (default)auto
existingContextNoBackground info or previous attempts
includeAnalysisNoInclude feasibility/impact analysis

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It mentions frameworks and analysis but does not indicate side effects, safety, or whether it's read-only. Only output hints are vague.

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?

Single sentence, to the point, but could be more structured with brief usage context. No wasted words.

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?

Given 10 parameters and no output schema, the description is too brief. It doesn't explain return format or how results are presented, omitting critical behavioral context.

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 has 100% description coverage, so baseline is 3. Description adds context about structured frameworks and domain context but does not enhance parameter understanding beyond schema descriptions.

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 generates creative ideas using structured frameworks with domain context and feasibility analysis. The verb is specific (generate) and resource is well-defined (creative ideas), with no sibling conflicts.

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?

No guidance on when to use this tool vs alternatives. The sibling tools are unrelated, but the description does not help an agent decide context for brainstorming use.

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