Skip to main content
Glama

get_threat_models_report

Retrieve threat modeling reports to analyze security risks and vulnerabilities within specified time periods.

Instructions

Get threat models report data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startNo
endNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler and registration for 'get_threat_models_report'. This function is decorated with @mcp.tool(), making it the primary tool implementation exposed via the MCP server. It creates an API client context and delegates to the client's get_threat_models_report method, returning the result as a string.
    @mcp.tool()
    async def get_threat_models_report(start: str = None, end: str = None) -> str:
        """Get threat models report data"""
        async with create_client_from_env() as client:
            result = await client.get_threat_models_report(start=start, end=end)
            return str(result)
  • Supporting helper method in the DeviciAPIClient class that implements the core logic for fetching the threat models report. It builds query parameters from start and end dates and performs an authenticated GET request to the Devici API endpoint '/reports/threat-models'.
    async def get_threat_models_report(
        self, 
        start: Optional[str] = None, 
        end: Optional[str] = None
    ) -> Dict[str, Any]:
        """Get threat models reports."""
        params = {}
        if start:
            params["start"] = start
        if end:
            params["end"] = end
        return await self._make_request("GET", "/reports/threat-models", params=params)
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure but provides none. It doesn't indicate whether this is a read-only operation, what format the report data takes, whether it's paginated or filtered, what permissions are required, or any rate limits. The description fails to disclose any behavioral traits beyond the basic action implied by 'get'.

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 maximally concise at just 5 words, with no wasted words or unnecessary elaboration. It's front-loaded with the core action and resource. While this conciseness comes at the expense of completeness, the description itself is structurally efficient with every word serving a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a tool with 2 parameters (0% schema coverage), no annotations, multiple similar sibling tools, and an output schema (which means the description doesn't need to explain return values), the description is completely inadequate. It fails to address the parameter meaning gap, provides no behavioral context, and offers no differentiation from alternatives. For a report-generation tool with date filtering parameters, this minimal description leaves critical questions unanswered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage for both parameters (start and end), and the tool description provides absolutely no information about what these parameters mean or how they should be used. The description doesn't mention that date filtering is available, doesn't explain what format the dates should be in, and doesn't clarify whether both parameters are required or optional. With 2 undocumented parameters and no compensation in the description, this is inadequate.

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

Purpose2/5

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

The description 'Get threat models report data' is a tautology that essentially restates the tool name 'get_threat_models_report'. It specifies the verb 'get' and resource 'threat models report data', but doesn't clarify what constitutes 'report data' versus regular threat model data available through sibling tools like 'get_threat_model' or 'get_threat_models'. The purpose remains vague about what distinguishes this report from other threat model retrieval operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance on when to use this tool versus alternatives. With multiple sibling tools for retrieving threat models (get_threat_model, get_threat_models, get_threat_models_by_collection) and no indication of what makes this 'report' different, there's no help for an agent to choose appropriately. No context, prerequisites, or exclusions are mentioned.

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