Skip to main content
Glama
Sign In
Repro Capsule MCP

Repro Capsule MCP

by efficjump
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

start_case

Starts a bug reproduction case with a redacted report, constrained to allowed project roots.

Instructions

Create a versioned case after constraining the project root and redacting the report.

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": {
      "name": "<name>",
      "project_root": "<project_root>",
      "bug_report": "<bug_report>"
    },
    "name": "start_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesShort human-readable name for the reproduction case.
bug_reportYesObserved failure report; credential-like text is redacted.
project_rootYesExisting project directory inside REPRO_CAPSULE_ALLOWED_ROOTS.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations (readOnlyHint=false, destructiveHint=false) are minimal, so the description carries the burden. It discloses two key behaviors: redaction of credential-like text and constraint of project root to allowed directories. This added context is valuable, though it does not cover all potential side effects or authorization needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-constructed sentence that immediately states the action ('Create a versioned case') and then adds essential qualifiers. No superfluous information; every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's three parameters, full schema coverage, and existence of an output schema, the description is sufficiently complete. It conveys the core purpose and key behavioral traits (redaction, constraint, versioning), providing enough context for an agent to decide when to invoke this 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%, so each parameter already has clear documentation. The tool description adds only a high-level summary of behavior (constraining, redacting) rather than parameter-specific details. With full schema coverage, a baseline of 3 is appropriate.

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 'Create a versioned case', which is a specific verb+resource combination. It distinguishes from sibling tools like list_cases and analyze_case by focusing on creation. The additional context 'after constraining the project root and redacting the report' clarifies the scope.

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?

The description does not provide any guidance on when to use this tool versus alternatives like add_artifact or plan_command. It implies prerequisites (constraining project root) but does not explicitly state conditions or exclusions.

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