Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

users-get-current

Retrieve your authenticated user profile from Shortcut project management to verify identity and access permissions for AI-assisted workflows.

Instructions

Get the current user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that fetches the current user using the ShortcutClientWrapper and formats the response using toResult.
    async getCurrentUser() {
    	const user = await this.client.getCurrentUser();
    
    	if (!user) throw new Error("Failed to retrieve current user.");
    
    	return this.toResult(`Current user:`, user);
    }
  • src/tools/user.ts:9-13 (registration)
    Registers the "users-get-current" tool on the CustomMcpServer instance, linking it to the getCurrentUser handler.
    server.addToolWithReadAccess(
    	"users-get-current",
    	"Get the current user",
    	async () => await tools.getCurrentUser(),
    );
  • BaseTools helper method used by the handler to format the output as an MCP CallToolResult with JSON-embedded content.
    protected toResult(
    	message: string,
    	data?: unknown,
    	paginationToken?: string | null | undefined,
    ): CallToolResult {
    	return {
    		content: [
    			{
    				type: "text",
    				text: `${message}${data !== undefined ? `\n\n<json>\n${JSON.stringify(data, null, 2)}\n</json>${paginationToken ? `\n\n<next-page-token>${paginationToken}</next-page-token>` : ""}` : ""}`,
    			},
    		],
    	};
    }
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. While 'Get' implies a read operation, it doesn't specify whether this requires authentication, what data is returned (e.g., user profile, permissions), or any rate limits. The description is too minimal to adequately inform behavioral expectations for a tool that likely involves user identity and access.

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 zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple tool with no parameters. Every word 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?

For a tool with 0 parameters, 100% schema coverage, and no output schema, the description is minimally complete. It states what the tool does but lacks details about return values, authentication requirements, or error conditions. Given the likely importance of user context in this system, more completeness would be beneficial despite the simple structure.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's purpose. This meets the baseline expectation for tools without 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 action ('Get') and resource ('the current user'), making the purpose immediately understandable. It distinguishes from sibling tools like 'users-list' by specifying 'current' user rather than listing all users. However, it doesn't explicitly contrast with 'users-get-current-teams', which might cause some ambiguity about sibling differentiation.

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 'current user', suggesting it should be used when information about the authenticated user is needed. However, it provides no explicit guidance on when to use this versus alternatives like 'users-list' or 'users-get-current-teams', nor does it mention any prerequisites or exclusions.

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/useshortcut/mcp-server-shortcut'

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