Skip to main content
Glama
Sign In
Repro Capsule MCP

Repro Capsule MCP

by efficjump
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

export_capsule

Export a bug reproduction capsule as a ZIP archive containing case metadata and reviewed artifacts for sharing or documentation.

Instructions

Create a ZIP containing only persisted case metadata and reviewed artifact contents.

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": {
      "case_id": "<case_id>"
    },
    "name": "export_capsule"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idYesIdentifier returned by start_case.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Description discloses that it creates a ZIP with specific contents, which is consistent with annotations (readOnlyHint=false, destructiveHint=false). However, it does not explain the output format, storage location, or any side effects. Minimal added value beyond annotations.

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?

Single well-structured sentence of 13 words, front-loaded with the key action and constraints. No wasted words.

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?

For a simple tool with one parameter and an output schema, the description covers the main behavior. However, it omits edge cases like missing artifacts or empty metadata, and lacks usage guidance.

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 coverage is 100% and the parameter 'case_id' has a clear description in the schema. The tool description adds no additional meaning beyond what the schema already provides.

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?

Description has a specific verb 'Create' and resource 'ZIP', with clear constraints on contents ('persisted case metadata and reviewed artifact contents'). It distinguishes from siblings like 'start_case' and 'list_cases' by focusing on export.

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 explicit guidance on when to use this tool versus alternatives. No mention of prerequisites (e.g., case must be started, artifacts must exist). Usage is implied but not clarified.

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