Skip to main content
Glama
Sign In
sprinty

sprinty

by ebursztein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sprint_detach

Detach an MCP session from its current Sprinty binding and stop the dashboard to end sprint tracking for that session.

Instructions

Detach this MCP session from its current Sprinty binding and stop the dashboard.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sprint_detach"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_tokenNo
client_agent_idNo
claim_generationNo
client_session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.2
    • addedInput schema / additionalProperties
      Added value: +false
    • 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. First observedv0.1.9

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description does add one important behavioral fact the schema can't express: the dashboard is stopped as a side effect. However, it says nothing about whether the binding is recoverable (e.g., via sprint_resume), what credentials are needed (agent_token), or what happens to claimed items.

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?

One compact sentence with the action front-loaded and the side effect appended. It declares the final outcome cleanly, though the dangling implication that the session becomes unusable could be made explicit.

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 teardown operation with four undocumented sensitive parameters, no annotations, and no output schema, the definition is thin. It covers the action and the dashboard side effect but omits auth requirements, reversibility, and failure behavior.

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

Parameters1/5

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

Four parameters with 0% schema description coverage, and the description mentions none of them. Critical inputs like agent_token, client_session_id, and claim_generation are left entirely unexplained in both structured fields and prose.

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 (detach) and resource (this MCP session from its Sprinty binding), plus a concrete side effect (stop the dashboard). An agent can distinguish it from read-style siblings, though it doesn't explicitly differentiate it from agent_detach, sprint_close, or sprint_archive.

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 on when to use this versus sprint_close, sprint_archive, or agent_detach, and no indication of prerequisites or post-conditions. The agent must infer that 'detach' is the teardown-for-this-session operation.

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