Skip to main content
Glama

get_collection

Retrieve a specific collection by its ID from the Devici MCP Server to access threat model data, security components, or mitigations.

Instructions

Get a specific collection by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for 'get_collection', registered via @mcp.tool() decorator. It creates an API client context and calls the client's get_collection method to fetch and return the collection data as a string.
    @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)
  • API client helper method that performs the authenticated HTTP GET request to the Devici API endpoint /collections/{collection_id} to retrieve the specific collection.
    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?

No annotations are provided, so the description carries full burden. It states a read operation ('Get'), implying it's likely safe, but doesn't disclose behavioral traits like authentication needs, rate limits, error handling, 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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized for a simple retrieval tool, with no wasted information.

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

Completeness4/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 mostly complete. However, it lacks behavioral context like error cases or prerequisites, which is a minor gap since annotations are absent.

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

Parameters4/5

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

The description adds meaning by specifying that the parameter 'collection_id' is used to retrieve 'a specific collection', clarifying its role beyond the schema's title 'Collection Id'. With 0% schema description coverage and only one parameter, this adequately compensates, though it could detail format or constraints.

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 collection by ID'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_collections' (plural) which likely retrieves multiple collections, leaving some ambiguity about when to use each.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get_collections' and 'get_threat_models_by_collection', the description offers no context on selection criteria, such as whether this is for single-item retrieval versus bulk operations.

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