Skip to main content
Glama

get_mitigations_by_threat

Retrieve security mitigations for a specific threat to address vulnerabilities and enhance protection measures.

Instructions

Get mitigations for a specific threat

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threat_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for 'get_mitigations_by_threat', decorated with @mcp.tool() for registration and execution. It creates an API client context and delegates to the client's get_mitigations_by_threat method, returning the result as string.
    @mcp.tool()
    async def get_mitigations_by_threat(threat_id: str) -> str:
        """Get mitigations for a specific threat"""
        async with create_client_from_env() as client:
            result = await client.get_mitigations_by_threat(threat_id)
            return str(result)
  • Supporting method in DeviciAPIClient class that makes the authenticated HTTP GET request to the Devici API endpoint /mitigations/threat/{threat_id} to fetch mitigations associated with the threat.
    async def get_mitigations_by_threat(self, threat_id: str) -> Dict[str, Any]:
        """Get all mitigations for specific threat."""
        return await self._make_request("GET", f"/mitigations/threat/{threat_id}")
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic action without revealing whether this is a read-only operation, if it requires authentication, what the output format might be, or if there are rate limits. For a tool with no annotation coverage, this is a significant gap in transparency.

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

Conciseness5/5

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

The description is extremely concise with a single, clear sentence that front-loads the essential information. There's no wasted language or unnecessary elaboration, making it efficient for quick understanding.

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?

Given the tool's low complexity (single parameter, no nested objects) and the presence of an output schema, the description is minimally adequate. However, with no annotations and 0% schema coverage, it should ideally provide more context about behavior or parameters to fully compensate for these gaps, especially since sibling tools suggest a broader ecosystem.

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 description implies that 'threat_id' is required to fetch mitigations, which aligns with the single parameter in the schema. However, with 0% schema description coverage, the description doesn't add any details about the parameter's format, constraints, or examples. It meets the baseline of 3 since it doesn't contradict the schema but doesn't compensate for the lack of schema documentation.

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 verb 'Get' and the resource 'mitigations for a specific threat', making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'get_mitigation' or 'get_mitigations', which appear to be related but potentially different in scope or function.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_mitigation' (singular) or 'get_mitigations' (plural without threat filter), nor does it specify prerequisites such as needing an existing threat ID. This leaves the agent with insufficient context for proper tool selection.

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/sdelements/devici-mcp'

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