Skip to main content
Glama
awslabs

Threat Modeling MCP Server

Official
by awslabs

add_assumption

Add assumptions to a threat model to define boundaries and constraints, with support for single and batch entries.

Instructions

Add a new assumption to the threat model. Supports batch operations via the 'items' parameter.

Assumptions are statements that we accept as true without requiring further validation. They help scope the threat model by establishing boundaries and constraints. For single item: provide description, category, impact, rationale directly. For batch: provide a list of assumption dicts in the 'items' parameter.

Args: ctx: MCP context for logging and error handling description: Description of the assumption (required for single item mode) category: Category of the assumption (required for single item mode) impact: Impact of the assumption on the threat model (required for single item mode) rationale: Rationale for making this assumption (required for single item mode) items: Optional list of assumption dicts for batch operation

Returns: A confirmation message with the assumption ID(s)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoOptional list of assumptions to add in batch. Each dict should contain 'description', 'category', 'impact', 'rationale'. When provided, individual parameters are ignored.
impactNoImpact of the assumption on the threat model (required for single item mode)
categoryNoCategory of the assumption (e.g., 'Network', 'Authentication', 'AWS Services') (required for single item mode)
rationaleNoRationale for making this assumption (required for single item mode)
descriptionNoDescription of the assumption (required for single item mode)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the burden. It discloses batch behavior, the return type (confirmation with ID(s)), and the semantic purpose of assumptions. Missing details like idempotency or error handling are minor for a create tool, so it earns a solid 4.

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 with an intro, explanatory paragraph, and clear args/returns sections. It is slightly verbose by repeating schema details and including the non-schema 'ctx' argument, but every sentence contributes to usability.

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 (single vs batch), the description fully explains both modes, parameter requirements, and return value. An output schema exists, so return details are not needed. The description leaves no critical gaps for an add tool.

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 coverage is 100%, but the description adds value by explaining single vs batch parameter usage and clarifying that individual params are ignored when 'items' is provided. It also lists the required fields for single item mode. The mention of 'ctx' (not in schema) is a minor inconsistency, but overall it enhances parameter understanding.

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 'Add a new assumption to the threat model,' which is a specific verb+resource statement. It clearly differentiates from sibling add_* tools (add_component, add_connection, etc.) by explicitly naming 'assumption' and the threat model context.

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?

It provides clear when-to-use guidance: single item mode vs batch mode, with explicit parameter requirements for each. While it doesn't name alternatives like update_assumption, the create operation is self-evident and the batch vs single distinction serves as usage context.

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/awslabs/threat-modeling-mcp-server'

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