Skip to main content
Glama
Sign In
bolt-mcp

bolt-mcp

by BrittainKnight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

bolt_scaffold_adapter

Generate an isolated JS/TS/Python adapter behind a canonical contract, then run real contract tests to verify the vendor export behaves correctly.

Instructions

Generate an isolated JS/TS/Python adapter and real contract tests. Both schemas need paired examples; select a callable vendor export.

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": {
      "slotId": "<slotId>",
      "inputSchema": "<inputSchema>",
      "outputSchema": "<outputSchema>"
    },
    "name": "bolt_scaffold_adapter"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotIdYes
languageNomjs
timeoutMsNo
entryPointNo
exportNameNo
inputSchemaYes
projectPathNoProject directory; defaults to the server project
outputSchemaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare a non-read-only, open-world, non-idempotent, non-destructive operation. The description adds that generation is isolated and that schemas require paired examples, but it does not explain where files are written, whether existing files are overwritten, or what side effects occur.

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?

The description is two tight sentences with the main action front-loaded, and every clause carries some relevant information. It is somewhat terse for an eight-parameter mutation tool, but it avoids filler.

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?

For a complex tool with eight parameters, nested schema objects, no output schema, and mutation annotations, the description is too sparse. It omits key required inputs and generated-file behavior that an agent would need to invoke the tool confidently.

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 only 13%, so the description must compensate. It adds meaning for language, the input/output schemas, and selecting a vendor export, but leaves slotId, timeoutMs, projectPath, and entryPoint/exportName behavior largely unexplained.

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?

The description gives a specific verb and resource: 'Generate an isolated JS/TS/Python adapter and real contract tests.' It clearly identifies the artifact and test output, though it does not explicitly differentiate itself from sibling tools such as bolt_verify_slot or bolt_surgical_harvest.

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?

It provides meaningful preconditions: both schemas need paired examples and a callable vendor export must be selected. However, it does not say when to use this tool versus sibling tools, nor does it describe when not to use it.

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