Skip to main content
Glama

get_teams

Retrieve teams from Devici with pagination controls to manage and organize security team data 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 and registration for 'get_teams'. This function is decorated with @mcp.tool() and delegates to the API client's get_teams method.
    @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)
  • Core implementation of get_teams in DeviciAPIClient class. Makes authenticated GET request to the /teams/ API endpoint with pagination parameters.
    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 full burden for behavioral disclosure. It mentions pagination behavior, which is valuable, but doesn't address other important aspects like authentication requirements, rate limits, error conditions, or what the output contains. For a read operation with zero annotation coverage, this leaves significant gaps.

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 at just 5 words, front-loading the core purpose immediately. Every word earns its place with no wasted text or unnecessary elaboration.

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 that an output schema exists (which should document return values), the description doesn't need to explain return values. However, for a tool with 2 parameters, 0% schema description coverage, and no annotations, the description provides only minimal context about pagination behavior. It's adequate as a basic listing tool description but lacks depth for optimal agent understanding.

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?

Schema description coverage is 0%, so the schema provides no parameter documentation. The description mentions 'pagination' which hints at the purpose of the 'limit' and 'page' parameters, but doesn't explain their specific semantics, defaults, or valid ranges. This adds some meaning but doesn't fully compensate for the coverage gap.

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 ('teams from Devici'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'get_team' (singular), which appears to fetch a single team versus this tool's paginated list approach.

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 mentions 'with pagination' which implies this tool is for retrieving multiple teams, but it provides no explicit guidance on when to use this versus 'get_team' or other sibling tools. No when-not-to-use or alternative recommendations are included.

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