Skip to main content
Glama
Sign In
bolt-mcp

bolt-mcp

by BrittainKnight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

bolt_surgical_harvest

Harvest explicit file paths from a local directory or sparse Git clone while preserving license files and SHA-256 provenance for traceable code reuse.

Instructions

Harvest explicit paths from a local directory or sparse Git clone, preserving licenses and SHA-256 provenance.

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>",
      "sourceRepoOrPath": "<sourceRepoOrPath>",
      "targetPaths": "<targetPaths>"
    },
    "name": "bolt_surgical_harvest"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotIdYes
projectPathNoProject directory; defaults to the server project
targetPathsYes
stripPatternsNo
sourceRepoOrPathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations disclose non-read-only, non-idempotent, open-world behavior, and the description usefully adds that licenses and SHA-256 provenance are preserved. However, for a write tool it omits critical behavior: what gets written and where (slot ledger?), whether existing target files are overwritten, and what happens on partial failure. The provenance mention is the only substantive addition.

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 dense sentence with no filler, front-loading the action and source. Slightly compressed to the point of under-specification, but structurally clean.

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?

Given five parameters, 20% schema coverage, no output schema, and mutation semantics, the one-sentence description leaves notable gaps (slot targeting, strip behavior, result shape). It is adequate to identify the tool's intent but not to invoke it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 20% (just projectPath has a description), so the description must compensate and does not. It hints at targetPaths ('explicit paths') and sourceRepoOrPath ('local directory or sparse Git clone') but says nothing about slotId, stripPatterns, or their formats and effects.

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 names a specific verb ('harvest') and resource ('explicit paths from a local directory or sparse Git clone'), plus the value-add of license and SHA-256 provenance preservation. It is clearly distinguishable from siblings like bolt_init_ledger or bolt_verify_slot, though 'harvest' remains jargon that requires inference about the actual copy operation.

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 when-to-use guidance is given, no prerequisites (e.g., whether a slot must already exist via bolt_init_ledger), and no exclusions relative to the six sibling tools. The agent must guess the workflow position of this tool.

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