Skip to main content
Glama

get_threat

Retrieve detailed information about a specific security threat by providing its unique ID, enabling targeted analysis and response planning.

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 the 'get_threat' tool. It creates an API client, calls get_threat on it with the provided threat_id, and returns the result as a string.
    @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)
  • API client helper method that implements the core logic for fetching a threat by ID via HTTP GET request to the Devici API endpoint /threats/{threat_id}.
    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}")
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 states the action ('Get') but lacks behavioral details: it doesn't specify if this is a read-only operation, what permissions are required, error handling (e.g., for invalid IDs), or response format. The description is minimal and misses key 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 a single, efficient sentence with zero waste—it directly states the tool's function without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loaded with the core action.

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 0% schema coverage, it lacks context on behavior, usage, and parameter details, making it incomplete for optimal agent understanding.

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 'by ID', which clarifies the 'threat_id' parameter's purpose, but adds no details on format, constraints, or examples. This provides basic meaning but doesn't fully address the coverage gap, 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.

Purpose4/5

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

The description clearly states the verb ('Get') and resource ('a specific threat by ID'), making the purpose immediately understandable. It distinguishes from sibling tools like 'get_threats' (plural) by specifying retrieval of a single threat, though it doesn't explicitly contrast with other threat-related tools like 'get_threats_by_component'.

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 prerequisites (e.g., needing a threat ID), exclusions, or comparisons to siblings like 'get_threats' (for listing) or 'get_threats_by_component' (for filtered retrieval).

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