Skip to main content
Glama
Mipiti
by Mipiti

preview_undo_composition

Preview the inverse operations or refusal reasons for undoing a lift or split event without changing state, enabling informed confirmation before committing an undo.

Instructions

Preview the inverse plan (or divergence refusal) for a prior composition event WITHOUT mutating any state. Read-only.

Read-only counterpart to undo_composition_event. Used by the confirmation flow so the operator sees what an undo would do before committing — either the inverse state operations the apply step will commit, or the enumerated reasons the divergence detector refuses the undo. Same {plan, refusal} return shape for both event types.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesEither the surrogate id of the forward ``lift_applied`` / ``split_applied`` activity event, or the structured ``lift_id`` / ``split_id`` carried in the event's payload — both lookups are supported.
model_idYesThe model whose composition view originated the event. Must match the ``threat_model_id`` carried by the cited activity event; the server rejects with 404 when a caller tries to undo a sibling model's event through a different model's URL.
event_typeYesWhich forward composition event to preview undoing. One of: - ``"lift"``: preview undo of a ``lift_applied`` event. The plan block carries the lift inverse operations — tombstone the lifted LCA entity, restore the source descendants' copies, rewrite CO references. - ``"split"``: preview undo of a ``split_applied`` event. The plan block carries the split inverse operations — restore at the ancestor, tombstone the duplicated copies on every target descendant.
server_versionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description explicitly states 'WITHOUT mutating any state' and 'Read-only,' making side effects clear. It also explains the return shape (plan or refusal) and why refusal happens, but does not fully detail the plan/refusal content or error handling.

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?

The description is well-structured and not overly long, but it repeats 'Same {plan, refusal} return shape for both event types.' in the second paragraph, which is redundant. Slight trimming would improve conciseness.

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?

The description provides sufficient context for when to use (confirmation flow), what to expect (plan or refusal), and why refusal might occur. It does not include the exact return schema, but that is not required given no output schema is provided.

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?

All parameters have detailed schema descriptions explaining their meaning and allowed values (e.g., event_type lift/split). The tool description adds no extra beyond these schema descriptions, so baseline 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 the tool previews the inverse plan or refusal without mutating state, and explicitly identifies as a read-only counterpart to undo_composition_event. It distinguishes the purpose (preview vs. apply) with specific language.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by the confirmation flow before committing an undo, and mentions 'read-only counterpart' to guide selection. However, it does not explicitly contrast with other preview tools or state alternatives, leaving some ambiguity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mipiti/mipiti-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server