Skip to main content
Glama
geoffwhittington

SD Elements MCP Server

get_current_user

Retrieve details of the currently authenticated user within the SD Elements MCP Server, enabling seamless integration with the security development lifecycle platform.

Instructions

Get information about the currently authenticated user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'get_current_user' tool. Decorated with @mcp.tool() for automatic registration with the FastMCP server. It retrieves the current authenticated user via the API client and returns the result as formatted JSON.
    @mcp.tool()
    async def get_current_user(ctx: Context) -> str:
        """Get current authenticated user"""
        global api_client
        if api_client is None:
            api_client = init_api_client()
        result = api_client.get_current_user()
        return json.dumps(result, indent=2)
  • Import statement in the main server file that loads the tools module, which in turn imports users.py and registers the get_current_user tool via its decorator.
    from . import tools  # noqa: F401
  • Wildcard import of the users module, which executes the @mcp.tool() decorator on get_current_user, registering the tool.
    from .users import *
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It states this is a read operation ('Get'), which is clear, but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or what specific user information is returned. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 any unnecessary words. It is front-loaded with the core action and resource, making it easy to parse quickly.

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's simplicity (0 parameters, no output schema), the description is adequate as a basic overview. However, with no annotations and no output schema, it lacks details on what user information is returned, which could be important for an agent to understand the tool's utility fully. It meets minimum viability but has clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. A baseline of 4 is applied as per the rules for tools with 0 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 ('information about the currently authenticated user'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_user', but the specificity about 'currently authenticated' provides some distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by specifying 'currently authenticated user', suggesting this tool should be used when information about the authenticated session is needed. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'get_user' or other user-related tools, leaving some ambiguity.

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