Skip to main content
Glama
Sign In

Stride — AI software delivery platform

by page.stride
OverviewDiscussionsAdmin

Assign story

stride.assign_story
DestructiveIdempotent

Assign or unassign a story (identify it by ticket key like "ORB-526" or UUID). Pass assigneeId (a workspace member UUID) to assign, or assigneeId=null to clear the assignee. Conflict-guarded — rejected if a human edited the story after your last read (pass force:true, only with the human's explicit approval, to overwrite it). For broader field edits use stride.update_story.

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": {
      "storyId": "<storyId>",
      "assigneeId": "<assigneeId>"
    },
    "name": "stride.assign_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoOverride a HUMAN_EDIT_AFTER_AGENT_SYNC conflict, overwriting the human's newer edit. Set true ONLY when the human has explicitly approved overwriting their change — the override is audit-logged.
storyIdYesStory ticket key like "ORB-526" (preferred) or a Stride UUID.
assigneeIdYesWorkspace member UUID to assign (ids from stride.list_project_members — never the agent's own bot user, which cannot hold assignments), or null to unassign.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say destructiveHint/idempotentHint without explaining why; the description adds the substantive behavior: a conflict guard that rejects writes when a human edited the story after the agent's last read, and an audit-logged override. That is operational context an agent cannot infer from structured fields.

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?

Three dense sentences, front-loaded with the action, then the parameter branches, then the guard and the sibling pointer. No filler and nothing deferred to the end that should be earlier.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers action, ID formats, assign/unassign branching, conflict behavior and the escape hatch, which is nearly everything needed for a 3-param mutation with no output schema. The one gap is that it never describes the result of a successful call (e.g., what is returned after the assignment or the conflict rejection payload).

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%, so storyId format, assigneeId UUID/null semantics and force are already fully documented. The description restates the null-to-unassign rule and ID format rather than adding new meaning, so baseline 3 applies.

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?

States the specific verb pair (assign/unassign) and resource (story), and explicitly distinguishes itself from stride.update_story for broader field edits. An agent can pick this tool without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit branch conditions: pass assigneeId to assign, null to clear, and use stride.update_story for other field changes. It also gates the force override on human explicit approval, which is the key decision the agent must make.

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

All Stride — AI software delivery platform toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources