Shortcut MCP Server

Get Shortcut Label

get_label

Retrieve a Shortcut label by its numeric ID to access label details for project management.

Instructions

Get a Shortcut label by numeric label ID.

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": {
      "label_id": "<label_id>"
    },
    "name": "get_label"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the basic 'Get' action and fails to explain what dry_run does, how missing IDs are handled, or what response format to expect. The presence of the dry_run parameter in the schema is a notable behavioral detail that the description ignores.

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, front-loaded sentence that immediately states the action and key parameter. It is concise with no filler or redundant phrasing. Every word earns its place.

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 description is too sparse for a tool with two parameters and no output schema or annotations. It fails to explain the dry_run parameter, expected return value, error behavior, or how it differs from list_labels. While the core 'get by ID' purpose is clear, the lack of behavioral and output context makes it incomplete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It adds 'numeric' and 'label ID' semantics for label_id, which is helpful. However, it completely omits dry_run, a parameter with no schema description or enum values, leaving the agent without any guidance on its purpose or acceptable values.

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 'Get a Shortcut label by numeric label ID' clearly states the verb (Get) and resource (Shortcut label) and specifies the lookup key (numeric label ID). This distinguishes it from siblings like list_labels, create_label, update_label, and delete_label, which focus on listing or mutating labels.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that this is for retrieving a single label by ID as opposed to listing labels, nor does it explain when dry_run might be useful. There is no when-not or alternative tool mention.

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

Deploy Server