Skip to main content
Glama

get_mitigations_by_threat

Retrieve security mitigations for a specific threat by providing its threat ID, enabling threat response planning and risk management.

Instructions

Get mitigations for a specific threat

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threat_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler function decorated with @mcp.tool(). It creates an API client using create_client_from_env, calls client.get_mitigations_by_threat(threat_id), and returns the stringified result.
    @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)
  • API client helper method that makes an authenticated HTTP GET request to the /mitigations/threat/{threat_id} endpoint to retrieve mitigations associated with the given threat ID.
    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}")
  • Shared helper method in API client for making authenticated HTTP requests to the Devici API, handling authentication if needed and error raising.
    async def _make_request(
        self, 
        method: str, 
        endpoint: str, 
        params: Optional[Dict[str, Any]] = None,
        json_data: Optional[Dict[str, Any]] = None
    ) -> Dict[str, Any]:
        """Make authenticated request to Devici API."""
        if not self.access_token:
            await self.authenticate()
            
        try:
            response = await self.client.request(
                method=method,
                url=endpoint,
                params=params,
                json=json_data
            )
            response.raise_for_status()
            return response.json()
            
        except httpx.HTTPError as e:
            logger.error(f"API request failed: {method} {endpoint} - {e}")
            raise
  • Factory function to create the DeviciAPIClient instance from environment variables, used by all tool handlers.
    def create_client_from_env() -> DeviciAPIClient:
        """Create API client from environment variables."""
        config = DeviciConfig(
            api_base_url=os.getenv("DEVICI_API_BASE_URL", "https://api.devici.com/api/v1"),
            client_id=os.getenv("DEVICI_CLIENT_ID", ""),
            client_secret=os.getenv("DEVICI_CLIENT_SECRET", ""),
            debug=os.getenv("DEBUG", "false").lower() == "true"
        )
        
        if not config.client_id or not config.client_secret:
            raise ValueError("DEVICI_CLIENT_ID and DEVICI_CLIENT_SECRET must be set")
            
        return DeviciAPIClient(config) 
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 what the tool does ('Get mitigations'), but doesn't describe whether it's read-only, requires authentication, has rate limits, or what the output format entails. This is inadequate for a tool with no annotation coverage.

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 sentence that directly states the tool's purpose. It's front-loaded and wastes no words, 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 has an output schema (which handles return values) and only 1 parameter, the description is minimally complete. However, with no annotations and sibling tools that could cause confusion, it lacks sufficient context for optimal agent use, especially regarding behavioral aspects.

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 mentions 'for a specific threat', which implies the 'threat_id' parameter is required to identify the threat. However, with 0% schema description coverage and only 1 parameter, the description adds minimal value beyond what the schema's title ('Threat Id') already suggests. The baseline is appropriate given the low parameter count.

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 understandable. However, it doesn't differentiate from sibling tools like 'get_mitigation' or 'get_mitigations', which could be confusing for an agent trying to select the right tool.

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 like 'get_mitigation' or 'get_mitigations'. It doesn't specify prerequisites, context, or exclusions, leaving the agent without clear usage instructions.

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

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