Skip to main content
Glama
Sign In
Threat Modeling MCP Server

Threat Modeling MCP Server

by residentevilrenz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

manage_assumptions

Manage threat modeling assumptions by adding, updating, listing, retrieving, or deleting records.

Instructions

Manage assumptions through one compact action-based tool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "manage_assumptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoBatch records for add or update
actionYesOperation: describe, add, update, list, get, or delete
valuesNoFields for one assumption or optional list filters
item_idNoAssumption ID for one get, update, or delete
item_idsNoAssumption IDs for batch delete

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden and discloses nothing: not that actions include mutation and deletion, not that batch delete exists via item_ids, not whether deletes are irreversible, and not what permissions are required. This is a significant gap for a tool with destructive capability.

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

Conciseness2/5

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

It is a single short sentence, but its brevity comes from under-specification rather than economy: no sentence conveys information an agent could act on. Front-loading is moot when there is essentially nothing to front-load.

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

Completeness2/5

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

For a five-parameter tool with six actions, batch inputs, and destructive delete paths, and with no annotations to offset the gap, the description should explain action semantics and mutation effects. The presence of an output schema excuses explaining return values, but almost nothing else is covered.

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% and all five parameters, including the action enum, are documented in the schema itself, so the baseline of 3 applies. The description adds no meaning beyond that, mentioning only that the tool is action-based.

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

Purpose2/5

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

"Manage assumptions through one compact action-based tool" restates the tool name and adds only that it is action-dispatched, which the schema already shows. It never says what an assumption is here, nor does it distinguish this tool from the many sibling manage_* tools such as manage_architecture or manage_threats.

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

Usage Guidelines1/5

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

There is no when-to-use, when-not-to-use, or alternative-selection guidance anywhere in the description, despite six distinct actions (including delete) that an agent must choose among. The agent gets no signal about how this tool relates to its many siblings.

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