Skip to main content
Glama

get_mitigations

Retrieve threat mitigation strategies from the Devici platform with paginated results to manage security controls effectively.

Instructions

Get mitigations from Devici with pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
pageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for the 'get_mitigations' tool. It is registered via the @mcp.tool() decorator and delegates to the API client to fetch paginated mitigations from the Devici API.
    @mcp.tool()
    async def get_mitigations(limit: int = 20, page: int = 0) -> str:
        """Get mitigations from Devici with pagination"""
        async with create_client_from_env() as client:
            result = await client.get_mitigations(limit=limit, page=page)
            return str(result)
  • The API client helper function that implements the core logic for retrieving mitigations via HTTP GET request to the Devici API endpoint with pagination parameters.
    async def get_mitigations(self, limit: int = 20, page: int = 0) -> Dict[str, Any]:
        """Get all mitigations."""
        params = {"limit": limit, "page": page}
        return await self._make_request("GET", "/mitigations/", params=params)
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 mentions 'with pagination', which hints at behavioral traits like handling large datasets, but doesn't disclose critical details such as rate limits, authentication needs, error handling, or what 'mitigations' entails (e.g., format, content). This is a significant gap 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.

Conciseness4/5

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

The description is a single, efficient sentence: 'Get mitigations from Devici with pagination'. It's front-loaded with the core action and includes key behavioral info (pagination), making it appropriately sized with no wasted words, though it could be more structured for clarity.

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 likely defines return values), the description doesn't need to explain outputs. However, with no annotations, 2 parameters, and low schema coverage, it's incomplete: it lacks context on when to use it, detailed parameter semantics, and full behavioral transparency. It's minimally viable but has clear gaps.

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 doesn't add meaning beyond the input schema, which has 2 parameters (limit, page) with 0% schema description coverage. It mentions 'pagination', implying the use of limit and page, but doesn't explain their semantics (e.g., default values, ranges, or how pagination works). With low schema coverage, the description compensates minimally, aligning with the baseline for partial compensation.

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 states the tool's purpose as 'Get mitigations from Devici with pagination', which includes a verb ('Get') and resource ('mitigations'), making it clear what it does. However, it doesn't distinguish it from sibling tools like 'get_mitigation' (singular) or 'get_mitigations_by_threat', leaving the scope vague beyond pagination.

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 mentions pagination, but doesn't specify contexts like retrieving all mitigations versus filtered ones (e.g., by threat), nor does it reference sibling tools for comparison, leaving usage unclear.

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