Skip to main content
Glama
geoffwhittington

SD Elements MCP Server

get_user

Retrieve detailed user information by specifying a user ID using the MCP Server’s API integration with SD Elements security platform.

Instructions

Get detailed information about a specific user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesThe ID of the user to retrieve

Implementation Reference

  • The primary handler function for the 'get_user' tool. It initializes the API client if necessary, calls api_client.get_user(user_id), and returns the result as formatted JSON. The @mcp.tool() decorator handles registration and schema inference from signature and docstring.
    @mcp.tool()
    async def get_user(ctx: Context, user_id: int) -> str:
        """Get details of a specific user"""
        global api_client
        if api_client is None:
            api_client = init_api_client()
        result = api_client.get_user(user_id)
        return json.dumps(result, indent=2)
  • Import statement in tools/__init__.py that loads the users module, executing the @mcp.tool() decorators to register the get_user tool.
    from .users import *
  • Import in server.py that loads the tools package, transitively importing users.py and completing tool registration before running the MCP server.
    from . import tools  # noqa: F401
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 states the tool retrieves detailed information, implying a read-only operation, but does not specify aspects like authentication requirements, rate limits, error handling, or what 'detailed information' entails (e.g., fields returned). This leaves significant gaps for a tool with no annotation coverage.

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 directly states the tool's purpose without unnecessary words. It is front-loaded and appropriately sized, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete for a tool that retrieves user details. It does not explain what information is returned (e.g., user attributes), potential errors, or behavioral traits like idempotency, leaving the agent with insufficient context for reliable use.

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 input schema has 100% description coverage, with the 'user_id' parameter clearly documented as an integer ID. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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 ('detailed information about a specific user'), making the purpose understandable. However, it does not differentiate from sibling tools like 'get_current_user' or 'list_users', which would require specifying it retrieves by ID rather than current session or listing multiple users.

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 does not mention sibling tools such as 'get_current_user' (for the authenticated user) or 'list_users' (for multiple users), leaving the agent to infer usage context without explicit direction.

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

Related 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/sde-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server