Skip to main content
Glama
Sign In
sprinty

sprinty

by ebursztein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sprint_resume

Binds the current MCP session to an existing sprint's git_dir and data_dir, letting you resume work without creating a new sprint.

Instructions

Resume an existing sprint by binding this MCP session to an existing git_dir and data_dir without creating a sprint.

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": {
      "git_dir": "<git_dir>"
    },
    "name": "sprint_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
git_dirYes
data_dirNo
agent_tokenNo
client_agent_idNo
claim_generationNo
client_session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.2
    • addedInput schema / properties / agent_token
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / claim_generation
      Added value: +{
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / client_agent_id
      Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / client_session_id
      Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed1 schema field changedv0.1.17
    • changedInput schema / required
      Previous value: -[
-  "git_dir",
-  "data_dir"
-]New value: +[
+  "git_dir"
+]
  3. First observedv0.1.9

TDQS

B3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It does disclose that the call binds the MCP session rather than creating a sprint, but says nothing about failure behavior if git_dir/data_dir don't match a sprint, what session state changes, auth/token requirements, or concurrency implications of claim_generation.

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?

A single front-loaded sentence with no filler; the core action and its key exclusion are both in the first clause.

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?

For a 6-parameter, session-mutating tool with no annotations, no output schema, and zero schema coverage, the description is too thin. An agent cannot tell what the call returns, what the four undocumented parameters do, or what state transition occurs.

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% across 6 parameters, so the description must compensate. It only names git_dir and data_dir (both required/relevant for locating the sprint) and leaves agent_token, client_agent_id, client_session_id, and claim_generation entirely unexplained.

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?

Specific verb+resource ("Resume an existing sprint") with an explicit contrast to sprint_new ("without creating a sprint"), so the agent can separate it from the creation sibling. It stops short of 5 only because "resume" vs "attach/claim" boundaries against sprint_detach/agent_attach are left implicit.

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 phrase "without creating a sprint" implies the create-new alternative, but no explicit when-to-use condition, prerequisites (e.g., sprint must already exist), or when-not-to-use guidance is given. Usage must be inferred.

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