Skip to main content
Glama

get_mitigation

Retrieve specific security mitigation details by ID to address vulnerabilities in threat models.

Instructions

Get a specific mitigation by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mitigation_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler function for 'get_mitigation'. Registers the tool via @mcp.tool() decorator and implements the logic by calling the API client to fetch mitigation data by ID and return as string.
    @mcp.tool()
    async def get_mitigation(mitigation_id: str) -> str:
        """Get a specific mitigation by ID"""
        async with create_client_from_env() as client:
            result = await client.get_mitigation(mitigation_id)
            return str(result)
  • Helper method in API client that performs the HTTP GET request to retrieve a specific mitigation by its ID from the Devici API.
    async def get_mitigation(self, mitigation_id: str) -> Dict[str, Any]:
        """Get specific mitigation by ID."""
        return await self._make_request("GET", f"/mitigations/{mitigation_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 states it's a read operation ('Get'), but doesn't mention authentication requirements, rate limits, error handling, or what happens if the ID doesn't exist. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 at just 5 words, front-loading the essential information with no wasted words. Every element ('Get', 'specific mitigation', 'by ID') contributes directly to understanding the tool's function.

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 one parameter, the description is minimally complete. However, with no annotations and multiple sibling tools, it should provide more context about differentiation and usage scenarios to be fully helpful.

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 0%, so the schema provides no parameter documentation. The description adds minimal value by indicating the parameter is a 'mitigation ID', but doesn't explain format, constraints, or examples. With only one parameter, the baseline is 4, but the lack of detail beyond the obvious reduces the score.

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 action ('Get') and resource ('a specific mitigation by ID'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_mitigations' (plural) which likely retrieves multiple mitigations, leaving some ambiguity about when to use each.

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 versus alternatives like 'get_mitigations' or 'get_mitigations_by_threat'. The description implies it's for retrieving a single mitigation by ID, but doesn't specify prerequisites, error conditions, or contextual limitations.

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