Skip to main content
Glama
Mipiti
by Mipiti

undo_lift_composition_event

Revert a previous composition lift by applying its inverse after re-running divergence detection, ensuring the target state hasn't materially changed.

Instructions

Apply the inverse of a previous lift_applied event.

Re-runs the divergence detector immediately before applying and refuses with 409 + the structured refusal block when state has materially evolved since the forward lift (assertions submitted on the lifted entity, downstream COs added that reference it, the entity edited, etc.). On success, persists the inverse state operations across the LCA + every affected source descendant and emits a structured lift_undone activity event citing original_event_id so the audit pack can chain undo to its forward.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lift_idYesEither the surrogate id of the ``lift_applied`` activity event, or the structured ``lift_id`` carried in the event payload.
model_idYesThe model whose composition view originated the lift. Must match the cited event's ``threat_model_id`` — the server rejects cross-model citations with 404.
server_versionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully carries behavioral disclosure. It details divergence detection, 409 refusal with structured block, conditions for refusal, success persistence actions, and audit event emission. This is comprehensive and goes beyond basic expectations.

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 appropriately detailed without being overly verbose. It is front-loaded with the main action and expands logically. Could be slightly more concise, but it effectively conveys necessary information.

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

Completeness5/5

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

Given the tool's complexity and the presence of an output schema, the description is complete. It covers all necessary aspects: purpose, conditions, effects, and audit trail. No gaps are evident for an agent to invoke correctly.

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?

The description does not add any information about the parameters beyond what is in the input schema. With 67% schema coverage, the description provides no additional parameter semantics, placing it at baseline.

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 it applies the inverse of a lift_applied event, specifying verb, resource, and key behaviors. It distinguishes from siblings like preview_undo_lift_composition by focusing on execution, though not explicitly contrasting.

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?

The description outlines when to use (undo a lift_applied event) and conditions for refusal (state evolution), but does not explicitly mention when not to use or suggest alternatives like the preview tool. The guidance is present but implied.

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