VibeTape MCP Server

Overview Schema Source Related Servers Discussions Admin

make_retex

Generate a structured RETEX with rules, bullets, and don'ts from a captured development moment to enable clear documentation and handoffs.

Instructions

Generate rule + bullets + dont from a captured moment

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": {
      "momentId": "<momentId>"
    },
    "name": "make_retex"
  }
}

Input Schema

Name	Required	Description	Default
`momentId`	Yes	ID of the moment to create RETEX from

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Aug 1, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Generate' and lists output components, but does not disclose whether this is a write operation, if it modifies the moment, requires any authorization, or what side effects might occur. This is a significant gap for a tool that likely creates a new RETEX artifact.

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 sentence that front-loads the action ('Generate') and the input ('from a captured moment'). Every word contributes to the core meaning, with no filler or redundant information.

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 generation tool with no output schema and no annotations, the description is too thin. It doesn't clarify what 'rule', 'bullets', and 'dont' are, nor the format or structure of the output. An agent would need to infer from sibling tools (e.g., get_retex_for_task) to understand what a RETEX is, and the description alone is insufficient to set expectations.

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%: the only parameter 'momentId' is described as 'ID of the moment to create RETEX from'. The description does not add additional meaning beyond the schema, which is acceptable per the baseline for high schema coverage, but it also doesn't clarify the format or origin of the momentId.

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 uses the specific verb 'Generate' and names the output components ('rule + bullets + dont') from a 'captured moment', which clearly distinguishes it from sibling tools like get_retex_for_task (retrieval) and export tools. However, the term 'dont' is ambiguous (likely meaning 'don'ts') and could be clearer.

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 gives no guidance on when to use this tool versus alternatives such as get_retex_for_task (which retrieves an existing RETEX) or generate_context_handoff. It neither states when to use it nor mentions any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.