Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

teams-list

Retrieve all teams from Shortcut project management to view team structure and members for project coordination.

Instructions

List all Shortcut teams

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/teams.ts:46-56 (handler)
    The main handler function for the "teams-list" tool. Fetches all teams using the Shortcut client and returns a formatted result, handling empty list case.
    	async getTeams() {
		const teams = await this.client.getTeams();

		if (!teams.length) return this.toResult(`No teams found.`);

		return this.toResult(
			`Result (first ${teams.length} shown of ${teams.length} total teams found):`,
			await this.entitiesWithRelatedEntities(teams, "teams"),
		);
	}
}
  • src/tools/teams.ts:26-30 (registration)
    Registration of the "teams-list" tool on the MCP server, with no input parameters, delegating to the getTeams() method.
    server.addToolWithReadAccess(
	"teams-list",
	"List all Shortcut teams",
	async () => await tools.getTeams(),
);

Tool Definition Quality

B3.2/5.0
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. It states it's a list operation but doesn't describe what 'all' means (e.g., pagination, filtering, sorting), whether it requires authentication, rate limits, or what the output format looks like. This is inadequate for a tool with zero 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 states exactly what the tool does without any unnecessary words. It's perfectly front-loaded and wastes no space, making it ideal for quick comprehension.

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 simple list tool with no parameters and no output schema, the description is minimally adequate but leaves important gaps. Without annotations, it should describe behavioral aspects like authentication requirements, pagination, or output format. The current description meets basic requirements but doesn't provide complete context for safe invocation.

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 zero parameters, and schema description coverage is 100% (empty schema is fully described as having no parameters). The description appropriately doesn't discuss parameters since none exist, earning a high baseline score for parameter semantics.

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 ('List all') and the resource ('Shortcut teams'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'teams-get-by-id' or 'users-get-current-teams', which would require more specific scope information 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. It doesn't mention when this tool is appropriate compared to 'teams-get-by-id' (for specific teams) or 'users-get-current-teams' (for teams associated with current user), leaving the agent without usage context.

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