Skip to main content
Glama
Sign In
sprinty

sprinty

by ebursztein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sprint_archive

Archive a sprint with a required recovery reason to bypass normal close gates when a sprint must be closed outside the standard workflow.

Instructions

Archive the sprint with a recovery reason, bypassing normal close gates.

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": {
      "reason": "<reason>"
    },
    "name": "sprint_archive"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
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. Addedv0.1.17
  3. Removedv0.1.15
  4. First observedv0.1.9

TDQS

B3.1/5.0
Behavior3/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. It does disclose one substantive behavioral trait beyond the name — that this path bypasses the normal close gates and requires a recovery reason — but says nothing about irreversibility, what happens to unfinished items, or auth/claim requirements for the four undocumented parameters.

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?

A single front-loaded sentence with no filler; the operation and its key qualifier come first. It is efficient but so short that it borders on under-specification rather than being trim.

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?

Five parameters with zero schema coverage, no annotations, and no output schema mean the description has to do nearly all the work — and a twelve-word sentence does not cover return behavior, side effects on sprint items, or the identity/claim parameters required for a successful call.

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 five parameters, yet the description only alludes to one ('reason') via 'recovery reason' and gives no format or meaning for agent_token, client_agent_id, client_session_id, or claim_generation. The description does not compensate for the near-total absence of schema documentation.

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?

States a specific verb and resource ('Archive the sprint') and adds distinguishing scope via 'bypassing normal close gates,' which implicitly separates it from sprint_close. It does not name the sibling explicitly, so differentiation requires a small inference.

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?

'with a recovery reason, bypassing normal close gates' hints that this is an escape-hatch path used when the normal close path is unavailable, which implies when to prefer sprint_close. However, no explicit when/when-not rule or named alternative is given, leaving the routing inference to the agent.

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