Skip to main content
Glama

get_users

Retrieve users from the Devici platform with pagination controls to manage and access user data efficiently.

Instructions

Get users from Devici with pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
pageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The primary MCP tool handler for 'get_users', registered via @mcp.tool() decorator. Executes the tool logic by calling the API client.
    @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)
  • Supporting API client method that performs the HTTP GET request to '/users/' endpoint to retrieve users with pagination.
    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?

No annotations are provided, so the description carries full burden. It mentions pagination, which hints at list behavior, but doesn't disclose critical details like authentication requirements, rate limits, error conditions, or what the output contains. For a read operation with zero annotation coverage, this leaves significant behavioral 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 a single, efficient sentence with no wasted words. It's front-loaded with the core purpose ('Get users from Devici') and adds necessary detail ('with pagination') without redundancy. Every part earns its place.

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, the description doesn't need to explain return values. However, with 2 parameters at 0% schema coverage and no annotations, the description is incomplete—it lacks details on authentication, errors, and parameter usage. It's minimally adequate but has clear gaps for a tool with pagination parameters.

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 description must compensate. It mentions 'pagination', which implicitly relates to the 'limit' and 'page' parameters, but doesn't explain their semantics (e.g., what 'page=0' means, default values, or valid ranges). This adds some context but falls short of fully documenting the parameters.

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 'users from Devici', making the purpose understandable. It also mentions 'with pagination', which adds useful context about the operation's scope. However, it doesn't distinguish this tool from its sibling 'get_user' (singular) or 'search_users', which is a minor gap.

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' (for a single user) or 'search_users' (for filtered searches). It mentions pagination, which implies use for bulk retrieval, but doesn't explicitly state this as a usage scenario or differentiate from siblings.

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