Skip to main content
Glama
Mipiti

Mipiti MCP Server

by Mipiti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delete Assertion

delete_assertion

Permanently remove an assertion from a control or assumption to retract erroneous or misaligned claims. Deleting drops its contribution to sufficiency; verification re-evaluates on later reads.

Instructions

Permanently delete a single assertion from a control or assumption. Mutating and destructive: the assertion record is removed, not soft-deleted, and its contribution to sufficiency/verification is dropped. It does NOT itself re-run verification; sufficiency is re-evaluated on subsequent reads.

Use to retract a claim that was submitted in error or that get_verification_report flagged as misaligned (off-topic for the control's current description). To add assertions use submit_assertions; to inspect them first use list_assertions. Only "own" assertions can be removed here — inherited assertions come from composed models and must be managed on their source model.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
model_idYesID of the threat model.
control_idNoID of the control the assertion belongs to (omit if it belongs to an assumption).
assertion_idYesID of the assertion to delete.
assumption_idNoID of the assumption the assertion belongs to (omit if it belongs to a control).
server_versionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.66.0
    • changedInput schema / properties / assumption_id / description
      Previous value: -"ID of the assumption (omit if using control_id)."New value: +"ID of the assumption the assertion belongs to (omit if it belongs to a control)."
    • changedInput schema / properties / control_id / description
      Previous value: -"ID of the control (omit if using assumption_id)."New value: +"ID of the control the assertion belongs to (omit if it belongs to an assumption)."
  2. Addedv0.62.2
  3. Removedv0.62.0
  4. First observedv0.57.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full disclosure burden and meets it thoroughly. It states the operation is mutating and destructive, that deletion is permanent and not soft-delete, that sufficiency contribution is dropped, that verification is not re-run, and that inherited assertions cannot be removed here.

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 dense but every sentence earns its place: the destructive behavior, the side-effect caveat, the intended use cases, the sibling alternatives, and the ownership limitation. The most important warning about permanent deletion is front-loaded in the first sentence.

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?

For a destructive mutation tool with no annotations, the description is complete. It covers use cases, side effects, behavioral nuances, and routing to alternatives, while the output schema handles return-value 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 description coverage is 80%, so the baseline is 3. The description adds contextual meaning about control versus assumption targets and the ownership restriction, but it does not materially expand on the individual parameters beyond what the schema already says.

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 states a specific verb and resource: 'Permanently delete a single assertion from a control or assumption.' It also clarifies scope (own assertions only) and distinguishes itself from related operations by naming submit_assertions and list_assertions as alternatives.

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

Usage Guidelines5/5

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

The description explicitly says when to use the tool: to retract erroneous claims or assertions flagged as misaligned by get_verification_report. It also names the add and inspect alternatives and states an important exclusion: inherited assertions must be managed on their source model.

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