Skip to main content
Glama

get_users

Retrieve users from the Devici platform with pagination controls to manage large datasets efficiently.

Instructions

Get users from Devici with pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
pageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler function for 'get_users', registered via @mcp.tool() decorator. It creates an API client and calls the client's get_users method.
    @mcp.tool()
    async def get_users(limit: int = 20, page: int = 0) -> str:
        """Get users from Devici with pagination"""
        async with create_client_from_env() as client:
            result = await client.get_users(limit=limit, page=page)
            return str(result)
  • Helper method in DeviciAPIClient that makes the HTTP GET request to the /users/ endpoint with pagination parameters.
    async def get_users(self, limit: int = 20, page: int = 0) -> Dict[str, Any]:
        """Get all users."""
        params = {"limit": limit, "page": page}
        return await self._make_request("GET", "/users/", 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 (a behavioral trait) but doesn't cover other important aspects like authentication requirements, rate limits, error conditions, or what the output contains. 'Get users' implies a read operation, but lacks details about permissions or side effects.

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 and includes the key behavioral trait (pagination) efficiently.

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 handles return values), 2 parameters with 0% schema coverage, and no annotations, the description is minimally adequate. It covers the basic purpose and hints at pagination behavior, but doesn't provide enough context about when to use it versus siblings or detailed parameter guidance.

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 relates to the 'limit' and 'page' parameters in the schema, but doesn't explain their semantics beyond what's implied. With 0% schema description coverage, the description adds some value by hinting at pagination, but doesn't fully compensate for the lack of parameter documentation (e.g., what 'page=0' means, maximum limits).

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 users from Devici with pagination' clearly states the verb ('Get'), resource ('users'), and system ('Devici'), with the additional detail about pagination. It distinguishes from 'get_user' (singular) by implying multiple users, but doesn't explicitly differentiate from 'search_users' which might be a sibling alternative.

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_user' (singular) or 'search_users'. It mentions pagination which hints at usage for large datasets, but doesn't specify when to choose this over other user-related tools in the sibling list.

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