Shortcut MCP Server

Get Shortcut Group

get_group

Get details for a specific Shortcut team or group by providing its UUID. Retrieve group information to manage projects effectively.

Instructions

Get a Shortcut team/group by UUID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "group_id": "<group_id>"
    },
    "name": "get_group"
  }
}

Input Schema

Name	Required	Description	Default
`dry_run`	No
`group_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

B3.2/5.0

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 only says 'Get a Shortcut team/group by UUID' and does not mention read-only behavior, error handling (e.g., 404 if not found), authorization requirements, or response format. The verb 'Get' implies read-only, but no additional behavioral context is disclosed.

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 sentence with no filler words. Every part ('Get', 'Shortcut team/group', 'by UUID') contributes to the meaning. It is appropriately sized for a simple get-by-ID tool.

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?

The tool has no output schema and no annotations, so the description should explain return behavior and all parameters. It clarifies group_id but does not mention what the response contains or the purpose of dry_run. The overall context is incomplete for an agent to understand the tool's full contract.

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 meaning to group_id by specifying it as a UUID, which is more informative than the schema's generic 'string' type. However, the dry_run parameter is entirely unmentioned. With 0% schema description coverage, the description only partially compensates for the lack of parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states exactly what the tool does: 'Get a Shortcut team/group by UUID.' The verb 'Get' is specific, the resource is clearly named, and the lookup method (by UUID) is specified. It is easily distinguished from sibling tools like list_groups (which lists all groups) and get_member (which retrieves a member).

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?

There is no guidance on when to use this tool versus alternatives. It does not mention list_groups for listing all groups or any other sibling tool for related operations. The phrase 'by UUID' is a parameter constraint, not a usage recommendation, so the description offers no when-to-use or when-not-to-use context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server