Skip to main content
Glama

get_mitigations

Retrieve security mitigations from Devici's threat management system with paginated results for efficient access to protection measures.

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 get_mitigations. It is decorated with @mcp.tool() for registration and executes the tool logic by calling the API client to fetch mitigations.
    @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)
  • Supporting API client method that handles the actual HTTP request to retrieve mitigations from the Devici API.
    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)
  • Initialization of the FastMCP server instance where all @mcp.tool() decorated functions are registered as MCP tools.
    mcp = FastMCP("devici-mcp-server")
  • Factory function used by the handler to create an authenticated API client from environment variables.
    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?

No annotations are provided, so the description carries full burden. It mentions pagination, which hints at list behavior, but fails to disclose critical traits like read-only vs. mutation, authentication needs, rate limits, error handling, or what 'mitigations' entail. The description is too sparse to inform safe or effective use beyond basic operation.

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 a single, efficient sentence with zero waste. It front-loads the core action ('Get mitigations') and includes key constraint ('with pagination'), making it appropriately sized for the tool's complexity. Every word earns its place, though brevity contributes to gaps in other dimensions.

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 2 parameters with 0% schema coverage, no annotations, and an output schema present, the description is incomplete. It covers the basic operation but lacks details on behavioral traits, parameter usage, and differentiation from siblings. The output schema may handle return values, but the description does not provide enough context for effective tool selection or invocation.

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 description must compensate. It mentions 'pagination', which implies the 'limit' and 'page' parameters, but does not explain their semantics, defaults, ranges, or interactions. The description adds minimal meaning beyond the schema's titles, leaving parameters largely undocumented. Baseline 3 applies as it hints at purpose without detail.

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 mitigations from Devici with pagination' states a verb ('Get'), resource ('mitigations'), and source ('from Devici'), but lacks specificity about what mitigations are or how they differ from sibling tools like 'get_mitigation' (singular) or 'get_mitigations_by_threat'. It distinguishes minimally by mentioning pagination, but the purpose remains vague without context on the resource type or domain.

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, which implies usage for listing multiple items, but does not specify scenarios, prerequisites, or exclusions compared to siblings like 'get_mitigations_by_threat' or 'get_mitigation'. Without explicit when/when-not instructions, usage is 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/sdelements/devici-mcp'

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