Skip to main content
Glama

get_threat

Retrieve detailed information about a specific security threat using its unique identifier. This tool helps security teams access threat data for analysis and response.

Instructions

Get a specific threat by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threat_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler for 'get_threat': decorated with @mcp.tool(), accepts threat_id (str), fetches the threat via API client, converts result to string and returns it.
    @mcp.tool()
    async def get_threat(threat_id: str) -> str:
        """Get a specific threat by ID"""
        async with create_client_from_env() as client:
            result = await client.get_threat(threat_id)
            return str(result)
  • Supporting API client method that executes the HTTP GET request to '/threats/{threat_id}' to retrieve threat details.
    async def get_threat(self, threat_id: str) -> Dict[str, Any]:
        """Get specific threat by ID."""
        return await self._make_request("GET", f"/threats/{threat_id}")
  • Core helper method in API client for making authenticated HTTP requests to the Devici API, used by get_threat.
    async def _make_request(
        self, 
        method: str, 
        endpoint: str, 
        params: Optional[Dict[str, Any]] = None,
        json_data: Optional[Dict[str, Any]] = None
    ) -> Dict[str, Any]:
        """Make authenticated request to Devici API."""
        if not self.access_token:
            await self.authenticate()
            
        try:
            response = await self.client.request(
                method=method,
                url=endpoint,
                params=params,
                json=json_data
            )
            response.raise_for_status()
            return response.json()
            
        except httpx.HTTPError as e:
            logger.error(f"API request failed: {method} {endpoint} - {e}")
            raise
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 of behavioral disclosure. It states the tool retrieves a threat by ID, implying a read-only operation, but doesn't disclose any behavioral traits like authentication requirements, error handling (e.g., what happens if the ID is invalid), rate limits, or response format. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 and front-loaded with the core purpose in a single, clear sentence. There is no wasted language or redundancy, making it efficient for quick understanding without unnecessary detail.

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 (one parameter) and the presence of an output schema (which handles return values), the description is minimally adequate. However, with no annotations and incomplete parameter semantics, it lacks context on behavioral aspects like error handling or authentication, making it somewhat incomplete for safe and effective use.

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 mentions 'by ID', which aligns with the single parameter 'threat_id' in the input schema, but adds minimal semantic value beyond what the schema already indicates (a string titled 'Threat Id'). With 0% schema description coverage, the description doesn't compensate by explaining the ID format, source, or constraints, leaving the parameter's meaning under-specified.

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 tool's purpose with a specific verb ('Get') and resource ('a specific threat by ID'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_threats' (plural) or 'get_threats_by_component', which retrieve multiple threats, leaving some ambiguity about when to use this singular retrieval tool versus those alternatives.

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 doesn't mention sibling tools like 'get_threats' for listing threats or 'get_threats_by_component' for filtered retrieval, nor does it specify prerequisites such as needing a valid threat ID. This lack of context leaves the agent to infer usage based on tool names alone.

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