Skip to main content
Glama

get_collections

Retrieve paginated collections from Devici to manage threat modeling resources, supporting limit and page parameters for controlled access.

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 for get_collections, decorated with @mcp.tool(). Creates a Devici API client and calls its get_collections method to fetch paginated collections.
    @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)
  • Helper method in DeviciAPIClient that makes a GET request to /collections/ endpoint with pagination parameters to retrieve collections data.
    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 adds useful context about handling large result sets, but doesn't cover other critical aspects like whether this is a read-only operation, authentication requirements, rate limits, error conditions, or what the output looks like. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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—a single sentence with no wasted words. It's front-loaded with the core purpose ('Get collections from Devici') and includes the key behavioral trait ('with pagination') efficiently. Every part of the sentence earns its place by conveying essential information without redundancy.

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 (2 simple parameters) and the presence of an output schema (which likely defines the return structure), the description is somewhat complete but has notable gaps. It covers the basic action and pagination behavior but lacks guidance on usage versus siblings and doesn't address authentication or error handling. With no annotations, it should do more to compensate, making it adequate but not fully comprehensive.

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 doesn't add any meaning beyond what the input schema provides—it doesn't explain what 'limit' or 'page' parameters do, their typical ranges, or how pagination works (e.g., zero-based indexing). With 0% schema description coverage, the schema only provides titles and types without descriptions. The description doesn't compensate for this gap, so it meets the baseline for minimal parameter info.

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 distinguishes from siblings like 'get_collection' (singular) by implying it retrieves multiple collections. However, it doesn't specify if this is a list-all operation or filtered, leaving some ambiguity compared to more specific 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 like 'get_collection' (singular), 'get_threat_models_by_collection', or 'search_users'. It mentions pagination, which hints at usage for large datasets, but doesn't explicitly state when to choose this over other collection-related tools or what scenarios it's best suited for.

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