Skip to main content
Glama

get_user

Retrieve user details by ID to access and manage user information within the Devici threat modeling platform.

Instructions

Get a specific user by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_user' MCP tool. It is registered via the @mcp.tool() decorator and executes the tool logic by calling the API client to fetch the user data and returning it as a string.
    @mcp.tool()
    async def get_user(user_id: str) -> str:
        """Get a specific user by ID"""
        async with create_client_from_env() as client:
            result = await client.get_user(user_id)
            return str(result)
  • Supporting helper method in the DeviciAPIClient class that performs the HTTP GET request to retrieve a specific user by ID from the Devici API.
    async def get_user(self, user_id: str) -> Dict[str, Any]:
        """Get specific user by ID."""
        return await self._make_request("GET", f"/users/{user_id}")
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. 'Get' implies a read operation, but it doesn't specify whether this requires authentication, what happens if the user doesn't exist, rate limits, or response format. The description is minimal and lacks crucial behavioral context for a tool that likely interacts with user data.

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 essential information ('Get a specific user') with no wasted words. Every element serves a purpose, making it efficient despite its brevity.

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) and only one parameter, the description's minimalism is somewhat acceptable. However, with no annotations and 0% schema coverage, it should provide more context about authentication needs, error conditions, or differentiation from siblings to be truly complete for a data retrieval tool.

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 adds some meaning by specifying 'by ID', which clarifies the purpose of the 'user_id' parameter. However, it doesn't explain format requirements (e.g., UUID, numeric ID) or constraints, leaving significant gaps in parameter understanding.

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 ('a specific user by ID'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_users' (plural) or 'search_users', which would require explicit comparison to earn 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 like 'get_users' or 'search_users'. It mentions 'by ID' which implies you need a specific user identifier, but doesn't explicitly state prerequisites or contrast with sibling tools that might serve similar purposes.

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