Skip to main content
Glama
Sign In
webEmbedding

webEmbedding

by jongko54
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

build_rebuild_scaffold

Generates a bounded rebuild scaffold from an existing capture bundle when exact reuse is unavailable, writing generated files and reports to an output directory.

Instructions

Generate a bounded rebuild scaffold from an existing capture bundle when exact reuse is unavailable.

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": {
      "capture_bundle": "<capture_bundle>"
    },
    "name": "build_rebuild_scaffold"
  }
}

Input Schema

NameRequiredDescriptionDefault
output_dirNoDirectory to write capture artifacts, generated files, and reports into; created if missing.
capture_bundleYesCapture bundle object returned by capture_reference_bundle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.13
    • addedInput schema / properties / capture_bundle / description
      Added value: +"Capture bundle object returned by capture_reference_bundle."
    • addedInput schema / properties / output_dir / description
      Added value: +"Directory to write capture artifacts, generated files, and reports into; created if missing."
  2. First observedv0.3.12

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds the precondition of reuse unavailability but says nothing about what 'bounded' constrains, that files and reports are written to disk, or that repeated invocation is non-idempotent — context the agent would still need.

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?

One sentence, front-loaded with the verb and artifact, with no filler or redundant restatement of the schema. It is efficient, though the terseness contributes to the ambiguity of 'bounded rebuild scaffold' rather than resolving it.

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?

This is a non-read-only tool that writes artifacts and reports to a directory and has no output schema, so the description must carry the burden of describing what is produced and where. It omits any mention of file output, scaffold contents, or failure behavior when the bundle is insufficient, leaving significant gaps for a write tool.

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% and both parameters (including the nested capture_bundle object with its provenance pointer to capture_reference_bundle) are documented in the schema. The description only echoes 'capture bundle' and adds no semantics for output_dir or for what shape the bundle must have, so baseline 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?

The description names a specific verb and artifact ('Generate a bounded rebuild scaffold') and its input ('from an existing capture bundle'), which separates it from siblings like plan_reproduction_path and build_reproduction_bundle. The terms 'bounded' and 'rebuild scaffold' are domain jargon that is never unpacked, so the agent knows the category of action but not concretely what is produced.

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?

'when exact reuse is unavailable' gives a triggering condition, which is real usage guidance. However, it never names the alternative to use when exact reuse IS available (e.g., clone_reference_url or build_reproduction_bundle), and gives no exclusions or prerequisites, leaving the agent to infer the routing decision from sibling names alone.

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