Skip to main content
Glama
awslabs

Threat Modeling MCP Server

Official
by awslabs

delete_crossing_point

Delete one or more crossing points from your system architecture using their IDs. Supports batch operations for removing multiple points at once.

Instructions

Delete a crossing point. Supports batch operations via the 'ids' parameter.

This tool deletes one or more crossing points from the system architecture. 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 crossing point to delete (required for single item mode) ids: Optional list of crossing point IDs for batch deletion

Returns: A confirmation message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoID of the crossing point to delete (required for single item mode)
idsNoOptional list of crossing point 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 must disclose behavior. It only mentions returning a confirmation message and does not state that deletion is irreversible or discuss side effects on related entities (e.g., connections). Additionally, it lists a 'ctx' parameter that is not in the input schema, which could mislead an agent.

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 contains redundancy, repeating that the tool deletes crossing points multiple times. While it is not overly long, the repetition wastes space and could be tightened to a more concise format.

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 a rich schema and output schema, the description covers the basic operation but misses important context: no mention of irreversibility, what happens if neither parameter is provided, or potential impacts on linked connections. This leaves gaps for an agent to safely use the tool.

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

Parameters2/5

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

The schema provides 100% coverage for parameters, so baseline is 3. However, the description introduces an undocumented 'ctx' parameter, which adds confusion. The descriptions for 'id' and 'ids' add minimal value since the schema already explains the batch behavior and ignoring 'id' when 'ids' is provided.

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 the tool deletes crossing points, using a specific verb and resource. It also mentions batch operations, distinguishing it from sibling CRUD tools like add_crossing_point or update_crossing_point.

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 explicit usage instructions for both single and batch deletion modes. However, it does not state when not to use the tool or mention any prerequisites or exclusions, but the context is clear enough.

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