Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

users-get-current-teams

Retrieve a list of teams where the current user is a member within the Shortcut project management platform.

Instructions

Get a list of teams where the current user is a member

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'users-get-current-teams' tool. Fetches all teams and the current user via the ShortcutClientWrapper, filters for non-archived teams that include the current user as a member, and formats the result using base tool methods.
    async getCurrentUserTeams() {
    	const teams = await this.client.getTeams();
    	const currentUser = await this.client.getCurrentUser();
    
    	if (!currentUser) throw new Error("Failed to get current user.");
    
    	const userTeams = teams.filter(
    		(team) => !team.archived && team.member_ids.includes(currentUser.id),
    	);
    	if (!userTeams.length) return this.toResult(`Current user is not a member of any teams.`);
    
    	if (userTeams.length === 1) {
    		const team = userTeams[0];
    		return this.toResult(
    			`Current user is a member of team "${team.name}":`,
    			await this.entityWithRelatedEntities(team, "team"),
    		);
    	}
    
    	return this.toResult(
    		`Current user is a member of ${userTeams.length} teams:`,
    		await this.entitiesWithRelatedEntities(userTeams, "teams"),
    	);
    }
  • Registers the 'users-get-current-teams' tool with the CustomMcpServer using addToolWithReadAccess, providing the name, description, and handler reference.
    server.addToolWithReadAccess(
    	"users-get-current-teams",
    	"Get a list of teams where the current user is a member",
    	async () => await tools.getCurrentUserTeams(),
    );
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 of behavioral disclosure. It states the tool retrieves a list but does not mention critical aspects like authentication requirements, rate limits, pagination, error handling, or the format of the returned list. For a read operation with zero annotation coverage, this is a significant gap in transparency.

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 redundant or verbose language. It is front-loaded and appropriately sized for its simple function, earning full marks for conciseness.

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. It does not explain what the returned list contains (e.g., team details, structure), how results are formatted, or any behavioral traits like authentication needs. For a tool with no structured data support, more context is needed to be fully helpful.

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% description coverage, so no parameter information is needed. The description appropriately does not discuss parameters, aligning with the schema. A baseline of 4 is applied as it compensates adequately for the lack of parameters by not introducing unnecessary details.

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 a list') and resource ('teams where the current user is a member'), making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like 'teams-list' (which likely lists all teams) or 'teams-get-by-id' (which retrieves a specific team), missing full sibling distinction.

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 such as 'teams-list' or 'users-get-current'. It lacks explicit when/when-not instructions or named alternatives, leaving usage context implied rather than clearly defined.

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