Skip to main content
Glama
awslabs

Threat Modeling MCP Server

Official
by awslabs

delete_threat_actor

Delete one or more threat actors from your threat model. Provide a single ID or use the ids parameter for batch deletion.

Instructions

Delete a threat actor. Supports batch operations via the 'ids' parameter.

This tool deletes one or more threat actors from the threat model. For single item: provide the id directly. For batch: provide a list of IDs in the 'ids' parameter.

Args: ctx: MCP context for logging and error handling id: ID of the threat actor to delete (required for single item mode) ids: Optional list of threat actor IDs for batch deletion

Returns: A confirmation message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoID of the threat actor to delete (required for single item mode)
idsNoOptional list of threat actor IDs to delete in batch. When provided, the 'id' parameter is ignored.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/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 basic delete behavior and return of a confirmation message, but omits crucial details such as permanence, cascading effects on linked entities, or error handling. The behavior when both 'id' and 'ids' are provided is left to the schema rather than the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with sections, but the opening sentence 'Delete a threat actor' is immediately repeated in the next sentence, creating redundancy. The Args and Returns sections also echo schema information without adding value. A more concise version would merge the redundant statements.

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

Completeness3/5

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

For a simple delete tool with an output schema, the description is adequate but not complete. It does not differentiate from clear_threat_actors for bulk deletion, nor does it mention preconditions (e.g., whether the actor must exist) or potential implications of deleting an actor that is referenced elsewhere.

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 input schema already covers both parameters with 100% description coverage, including the precedence of 'ids' over 'id'. The description adds redundant mode explanations but does not introduce new semantic details beyond the schema. The mention of 'ctx' as an argument not present in the schema could cause confusion.

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 'Delete a threat actor' with a specific verb and resource, and explicitly mentions batch operations. This distinguishes it from sibling tools like add, update, list, or get threat actors.

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 provides clear context on when to use single vs batch deletion via the 'id' and 'ids' parameters. However, it does not contrast this tool with alternative bulk operations like clear_threat_actors or reset_threat_actors.

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