Skip to main content
Glama

get_collections

Retrieve paginated collections from the Devici security platform to manage and organize threat models, components, and mitigations.

Instructions

Get collections from Devici with pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
pageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler and registration for 'get_collections'. This is the primary entry point for the tool, decorated with @mcp.tool(), which registers it and defines its execution logic by delegating to the API client.
    @mcp.tool()
    async def get_collections(limit: int = 20, page: int = 0) -> str:
        """Get collections from Devici with pagination"""
        async with create_client_from_env() as client:
            result = await client.get_collections(limit=limit, page=page)
            return str(result)
  • Core implementation of get_collections in the DeviciAPIClient class. Performs the HTTP GET request to the '/collections/' endpoint with pagination parameters using the shared _make_request helper.
    async def get_collections(self, limit: int = 20, page: int = 0) -> Dict[str, Any]:
        """Get all collections."""
        params = {"limit": limit, "page": page}
        return await self._make_request("GET", "/collections/", params=params)
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 mentions 'with pagination', which hints at a list operation with limits, but doesn't describe key behaviors like whether it's read-only (implied by 'Get'), error conditions, authentication needs, rate limits, or what the output contains. For a tool with no annotation coverage, this leaves significant gaps in understanding its operation.

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 front-loads the core action ('Get collections from Devici') and adds a key detail ('with pagination'). There's no wasted text, and it's appropriately sized for a simple retrieval tool, making it easy to parse quickly.

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 has an output schema (which should cover return values), the description's job is reduced. It adequately states the purpose and hints at pagination. However, with no annotations and 0% schema description coverage, it lacks details on behaviors and parameter semantics. For a basic list tool, it's minimally viable but could benefit from more context on usage and limitations.

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 'pagination', which aligns with the parameters 'limit' and 'page' in the schema, adding context about their purpose. However, with 0% schema description coverage, the schema provides no details on these parameters. The description compensates slightly by implying pagination but doesn't explain semantics like default values, ranges, or units, leaving parameters partially undocumented.

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 ('collections from Devici'), making the purpose understandable. It also mentions 'with pagination', which adds specificity about the retrieval mechanism. However, it doesn't explicitly differentiate from sibling tools like 'get_collection' (singular) or 'get_threat_models_by_collection', which might retrieve related data.

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 scenarios like retrieving all collections versus filtered ones, or compare it to siblings such as 'get_collection' (singular) or 'get_threat_models_by_collection'. There's no indication of prerequisites, context, or exclusions for usage.

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