Skip to main content
Glama
ampcome-mcps

Shortcut MCP Server

by ampcome-mcps

list-teams

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

Instructions

List all Shortcut teams

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implements the core logic for the list-teams tool by fetching all teams from the Shortcut client, handling empty results, and formatting the output using base tool methods.
    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"),
    	);
    }
  • Registers the 'list-teams' tool on the MCP server with no input parameters and a handler that delegates to the getTeams method.
    server.tool("list-teams", "List all Shortcut teams", async () => await tools.getTeams());
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 (implied read-only) but doesn't mention pagination, sorting, rate limits, authentication needs, or what 'all' means in practice. This leaves significant behavioral gaps for a tool that likely returns multiple items.

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 with zero wasted words. It's front-loaded and appropriately sized for a simple list operation.

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 no annotations, no output schema, and multiple sibling tools, the description is insufficiently complete. It doesn't explain what data is returned (team objects? just names?), how results are structured, or how this differs from related tools like 'get-team'. For a list operation in a collaborative tool context, more context is needed.

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 with 100% schema description coverage, so the schema already fully documents the input. The description appropriately doesn't add parameter information, maintaining focus on the tool's purpose. Baseline for zero parameters is 4.

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 resource ('Shortcut teams'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get-team' (singular) or 'list-members' (different resource), which prevents 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 like 'get-team' (singular team) or 'list-members' (team members). There's no mention of prerequisites, context, or exclusions, leaving usage entirely implicit.

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/ampcome-mcps/shortcut-mcp'

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