Skip to main content
Glama

get_collection

Retrieve a specific collection by its ID from the Devici threat modeling platform to access and manage threat modeling resources.

Instructions

Get a specific collection by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler for 'get_collection'. This is the main execution function decorated with @mcp.tool(), which also registers it. It creates an API client and calls the helper to fetch the collection data.
    @mcp.tool()
    async def get_collection(collection_id: str) -> str:
        """Get a specific collection by ID"""
        async with create_client_from_env() as client:
            result = await client.get_collection(collection_id)
            return str(result)
  • Supporting API client method that makes the HTTP GET request to the Devici API endpoint for retrieving a specific collection by ID.
    async def get_collection(self, collection_id: str) -> Dict[str, Any]:
        """Get specific collection by ID."""
        return await self._make_request("GET", f"/collections/{collection_id}")
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves data ('Get'), implying a read operation, but doesn't specify if it's safe, requires authentication, has rate limits, or what happens if the ID is invalid. This leaves significant gaps 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.

Conciseness5/5

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

The description is extremely concise and front-loaded, consisting of a single, direct sentence that states the core purpose without any wasted words. It efficiently communicates the essential information in minimal space.

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 (1 parameter, no nested objects) and the presence of an output schema (which handles return values), the description is somewhat complete for basic use. However, with no annotations and minimal behavioral details, it lacks depth for safe and effective invocation in a broader context.

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 adds minimal meaning beyond the input schema: it clarifies that 'collection_id' is used to identify a specific collection. With 0% schema description coverage and 1 parameter, this provides some context, but it's basic and doesn't detail format or constraints, aligning with the baseline for low coverage.

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 action ('Get') and resource ('a specific collection by ID'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_collections' (plural) which likely retrieves multiple collections, so it's not fully distinguished.

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_collections' for listing multiple collections or 'get_threat_models_by_collection' for related data, leaving the agent without context for selection.

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