Skip to main content
Glama

get_teams

Retrieve teams from the Devici platform with pagination support to manage threat modeling resources efficiently.

Instructions

Get teams from Devici with pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
pageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler for 'get_teams': decorated with @mcp.tool(), fetches teams via API client and returns as string.
    @mcp.tool()
    async def get_teams(limit: int = 20, page: int = 0) -> str:
        """Get teams from Devici with pagination"""
        async with create_client_from_env() as client:
            result = await client.get_teams(limit=limit, page=page)
            return str(result)
  • API client helper method that performs the HTTP GET request to retrieve teams from the Devici API.
    async def get_teams(self, limit: int = 20, page: int = 0) -> Dict[str, Any]:
        """Get all teams."""
        params = {"limit": limit, "page": page}
        return await self._make_request("GET", "/teams/", params=params)
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 mentions pagination, which is useful context, but fails to describe other critical traits such as whether this is a read-only operation, any authentication requirements, rate limits, error handling, or the structure of returned data. For a tool with two parameters and an output schema, 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 a single, efficient sentence that front-loads the core purpose ('Get teams from Devici') and adds essential detail ('with pagination') without unnecessary words. Every part earns its place, making it highly concise and well-structured for quick comprehension.

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 parameters, no nested objects) and the presence of an output schema, the description is minimally adequate. It covers the basic action and pagination but lacks details on behavioral traits and parameter semantics. With no annotations, it should do more to explain usage and constraints, but the output schema mitigates some completeness needs.

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

Parameters2/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 for undocumented parameters. It mentions 'pagination' but doesn't explain the specific parameters 'limit' and 'page' or their semantics (e.g., what 'page' 0 means, default values, or valid ranges). This adds minimal value beyond the schema's titles, failing to adequately clarify parameter usage.

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 'Get teams from Devici with pagination' clearly states the action (Get), resource (teams), and system (Devici), with the addition of pagination as a key feature. It distinguishes from sibling 'get_team' (singular) by implying it retrieves multiple teams. However, it doesn't explicitly differentiate from other list-like siblings like 'get_collections' or 'get_users', keeping it from a perfect score.

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 when to choose 'get_teams' over 'get_team' (singular) or other retrieval tools like 'get_collections', nor does it specify prerequisites or exclusions. The mention of pagination hints at usage for large datasets but lacks explicit context.

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