Skip to main content
Glama

get_mitigation

Retrieve a specific security mitigation by its unique ID from the Devici threat modeling platform to access detailed protection measures and implementation guidance.

Instructions

Get a specific mitigation by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mitigation_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The primary MCP tool handler for 'get_mitigation'. Decorated with @mcp.tool() for automatic registration and schema inference from signature. Creates an authenticated API client and calls get_mitigation on it, converting result to 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)
  • API client helper method implementing the core logic: authenticated GET request to the Devici API endpoint /mitigations/{mitigation_id}.
    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?

No annotations are provided, so the description carries the full burden. It states it's a read operation ('Get'), but doesn't disclose behavioral traits such as error handling (e.g., what happens if the ID is invalid), authentication needs, rate limits, or the format of the returned data. The description is minimal and lacks essential operational context.

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, direct sentence that front-loads the core purpose. There is no wasted language, and it efficiently communicates the basic action without unnecessary elaboration.

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, read operation) and the presence of an output schema, the description is minimally adequate. However, with no annotations and 0% schema coverage, it lacks context on error cases, authentication, or data format, leaving gaps that could hinder effective use by an AI agent.

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 adds no meaning beyond the input schema, which has 0% description coverage. It mentions 'by ID' which aligns with the 'mitigation_id' parameter, but provides no additional details like ID format, examples, or constraints. With one parameter and no schema descriptions, the baseline is 3 as the description doesn't compensate for the coverage gap.

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

Purpose3/5

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

The description 'Get a specific mitigation by ID' clearly states the action (get) and resource (mitigation), but it's vague about what a 'mitigation' entails in this context. It distinguishes from sibling 'get_mitigations' by specifying retrieval of a single item, but doesn't explain what distinguishes a mitigation from other resources like threats or components.

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. It doesn't mention prerequisites (e.g., needing a valid mitigation ID), when not to use it, or how it differs from related tools like 'get_mitigations' or 'get_mitigations_by_threat' beyond the single vs. multiple item distinction implied in the name.

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