Skip to main content
Glama
Sign In
Shortcut MCP Server

Shortcut MCP Server

Official
by useshortcut
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

Stories: Unassign Current User

stories-unassign-current-user

Remove current user as the owner of a story by providing its unique story ID.

Instructions

Remove current user as story owner.

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": {
      "storyPublicId": "<storyPublicId>"
    },
    "name": "stories-unassign-current-user"
  }
}

Input Schema

NameRequiredDescriptionDefault
storyPublicIdYesStory ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.1
    • changedInput schema / properties / storyPublicId / description
      Previous value: -"The public ID of the story"New value: +"Story ID"
  2. Addedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations do not provide destructive or safety hints, and the description does not disclose side effects, failure conditions, or what happens if the current user is not the owner. For a mutation tool, more transparency is needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise and front-loaded, but borderline too brief for full clarity. No wasted words.

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?

Missing output schema and insufficient behavioral context. For a simple tool, the description does not cover what happens on success/failure or edge cases like unassignment of a user who is not the owner.

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?

Schema coverage is 100% with one parameter described as 'Story ID'. The description adds no extra meaning, so baseline score of 3 is appropriate.

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 'Remove current user as story owner' clearly states the action (remove) and the resource (current user as story owner), distinguishing it from the sibling tool 'stories-assign-current-user'.

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?

No explicit guidance on when to use or not use this tool. The context is clear given the naming, but lacks details like prerequisites or alternatives beyond the sibling list.

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

Deploy Server

Other Tools