Skip to main content
Glama
Mipiti
by Mipiti

Add Assumption

add_assumption

Add an assumption to a threat model, creating a new model version. Optionally attach an exclusion predicate to resolve indeterminate control outcomes by marking them unreachable.

Instructions

Add an assumption. Creates a new model version.

Assumptions represent security properties outside the system owner's trust boundary. When linked to COs and attested, they mitigate those COs in the assessment.

Optionally attach a structured exclusion predicate (the exclusion_* params). The reachability composer matches active

  • attested assumptions with predicates against COs deterministically — class-3 (deterministic computation) evidence in addition to the operator-attested class-1 evidence. Pass any subset of the fields; unspecified fields default to wildcard ("*"). When exclusion_co_ids is non-empty, it takes precedence over the match fields.

Use this to resolve a CO whose composer verdict is indeterminate because no structural primitive backs an operator non-applicability claim: set exclusion_co_ids=<co_id> (and optionally the attacker/asset/property fields), and the composer will derive unreachable / reason: assumption_excludes on subsequent loads, with the assumption's structured predicate as the audit-trail cause.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
model_idYesID of the threat model.
descriptionYesWhat is assumed (e.g., "Customer restricts CI runner egress").
linked_co_idsNoOptional comma-separated CO IDs this assumption covers.
server_versionYes
assumption_typeNo"external" (default, allows manual attestation) or "non_applicability" (requires CI verification, no manual attestation).external
exclusion_co_idsNoComma-separated CO IDs the predicate matches explicitly. When non-empty, overrides the match fields.
exclusion_asset_idNo"*" or concrete asset ID.
exclusion_attacker_idNoPredicate match — "*" wildcard (default when any other exclusion_* param is set) or concrete attacker ID.
exclusion_property_matchNo"C" | "I" | "A" | "U" | "*".
exclusion_attacker_vectorNoOne of "Network" | "Adjacent" | "Local" | "Physical" | "*".
exclusion_asset_component_idNo"*" or concrete component ID.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.62.2
  2. Removedv0.62.0
  3. First observedv0.57.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the mutation side effect, the attestation/mitigation lifecycle, deterministic class-3 evidence behavior, wildcard defaults, and precedence rules. This is strong behavioral context, though it does not cover operational concerns like permissions or reversibility.

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 front-loaded with the core action and side effect, then organizes the advanced exclusion predicate behavior into a focused section. It is fairly long, but the content earns its place given the tool's complexity and 11 parameters.

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 complex tool with no annotations, an output schema, and high schema coverage, the description covers the essential operational context: side effects, matching behavior, defaults, precedence, and a concrete use case. It does not spell out every assumption lifecycle step, but the schema and output schema cover the structured details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 91%, setting a high baseline. The description adds meaningful semantics beyond the schema: it explains that any subset of exclusion_* fields can be passed, unspecified fields default to wildcard, exclusion_co_ids takes precedence, and the predicate feeds deterministic composer evidence. This exceeds the 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 opens with a specific verb and resource: "Add an assumption." and clearly states the side effect "Creates a new model version." This distinguishes add_assumption from related operations like edit_assumption without relying on the title alone.

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 gives a concrete, decision-relevant scenario: use this to resolve a CO with an "indeterminate" composer verdict by setting exclusion_co_ids. It provides clear context for when the exclusion_* predicate mechanism is appropriate, though it does not explicitly name alternatives or state when not to use the tool.

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