Skip to main content
Glama
awslabs

Threat Modeling MCP Server

Official
by awslabs

set_threat_actor_relevance

Set a threat actor's relevance to the system by ID and boolean value, confirming the change.

Instructions

Set the relevance of a threat actor.

This tool sets whether a threat actor is relevant to the system.

Args: ctx: MCP context for logging and error handling id: ID of the threat actor is_relevant: Whether the threat actor is relevant to the system

Returns: A confirmation message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the threat actor
is_relevantYesWhether the threat actor is relevant to the system

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 must carry the full burden. It indicates a mutation ('set') and states the return value ('confirmation message'), but does not disclose whether this is an update to an existing record, what side effects occur, or error conditions. For a mutating tool with no annotations, more behavioral detail is needed.

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 Args and Returns sections, but it contains redundancy: the first and second sentences say nearly the same thing. The Args section duplicates schema information, adding length without additional value.

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?

The tool is simple, and the description includes the return value and parameter intent. However, it lacks usage context relative to sibling threat-actor tools (e.g., why a dedicated 'relevance' setter vs update_threat_actor) and does not cover prerequisites or edge cases. The output schema is mentioned as existing, which helps.

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 100%, so the baseline is 3. The description repeats the parameter descriptions from the schema without adding new information. It also mentions 'ctx' which is not in the input schema, potentially adding noise.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function with a specific verb ('Set') and resource ('relevance of a threat actor'), distinguishing it from sibling set_threat_actor_priority. It repeats the purpose in the second sentence, which is slightly redundant but not confusing.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool compared to related tools like update_threat_actor or set_threat_actor_priority. It does not mention prerequisites (e.g., the threat actor must already exist) or alternatives.

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