Skip to main content
Glama
ampcome-mcps

Shortcut MCP Server

by ampcome-mcps

get-team

Retrieve team details from Shortcut project management using the team's public ID to access member information and project data.

Instructions

Get a Shortcut team by public ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamPublicIdYesThe public ID of the team to get

Implementation Reference

  • Implements the core logic for the 'get-team' tool: fetches the team by public ID using the client, handles not found case, and formats the response with related entities.
    async getTeam(teamPublicId: string) {
    	const team = await this.client.getTeam(teamPublicId);
    
    	if (!team) return this.toResult(`Team with public ID: ${teamPublicId} not found.`);
    
    	return this.toResult(`Team: ${team.id}`, await this.entityWithRelatedEntities(team, "team"));
    }
  • Input schema for the 'get-team' tool using Zod: requires a string teamPublicId.
    { teamPublicId: z.string().describe("The public ID of the team to get") },
  • Registers the 'get-team' tool with the MCP server, including description and handler lambda that delegates to getTeam method.
    server.tool(
    	"get-team",
    	"Get a Shortcut team by public ID",
    	{ teamPublicId: z.string().describe("The public ID of the team to get") },
    	async ({ teamPublicId }) => await tools.getTeam(teamPublicId),
    );
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 team but doesn't describe what information is returned, error conditions (e.g., invalid ID), authentication needs, rate limits, or whether it's a read-only operation. For a tool 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 front-loads the core purpose without any wasted words. It's appropriately sized for a simple retrieval tool, making it easy to parse quickly.

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 a simple parameter with full schema coverage, the description is incomplete. It doesn't explain what data is returned, error handling, or behavioral traits, which are crucial for a retrieval tool. The conciseness comes at the cost of missing contextual details needed for effective use.

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

Parameters3/5

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

The description adds that the parameter is for getting a team by public ID, but the input schema already fully documents the single parameter 'teamPublicId' with 100% coverage. No additional semantic details (e.g., format examples, where to find the ID) are provided, so it doesn't add value beyond the schema, resulting in the baseline score.

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 ('a Shortcut team'), specifying it's by public ID. It distinguishes from siblings like 'list-teams' by focusing on a single team retrieval rather than listing multiple teams. However, it doesn't explicitly contrast with other get-* tools like 'get-story' or 'get-epic' beyond the resource type.

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 when you need a specific team by its public ID, but doesn't provide explicit guidance on when to use this versus alternatives like 'list-teams' for browsing or other get-* tools for different resources. No exclusions or prerequisites are mentioned, leaving usage context somewhat 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/ampcome-mcps/shortcut-mcp'

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