Skip to main content
Glama
Sign In
sprinty

sprinty

by ebursztein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

item_add

Add an atomic sprint item with a bounded title and description, required code locations, and execution gates so agents can track and validate work in a structured sprint ledger.

Instructions

Add an atomic item (bounded title, bounded description, code locations, gates — all required; gate_timeout_ms defaults to 5000 and null disables it).

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": {
      "subsprint": "<subsprint>",
      "title": "<title>",
      "description": "<description>",
      "code_locations": "<code_locations>",
      "gates": "<gates>"
    },
    "name": "item_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
gatesYes
titleYes
subsprintYes
agent_tokenNo
descriptionYes
dependenciesNo
high_priorityNo
code_locationsYes
client_agent_idNo
gate_timeout_msNo
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.18
    • addedInput schema / properties / gate_timeout_ms
      Added value: +{
+  "anyOf": [
+    {
+      "exclusiveMinimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
  3. Addedv0.1.17
  4. Removedv0.1.15
  5. First observedv0.1.9

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses that several fields are required and that gate_timeout_ms defaults to 5000 with null disabling it, but it omits permissions, side effects, failure behavior, and whether the item must belong to an existing subsprint.

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?

The description is a single front-loaded sentence with no filler. Every clause adds a required-field or timeout-default detail, and the core action appears first.

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?

This is a 12-parameter creation tool with a nested gates array, no annotations, no output schema, and 0% schema description coverage. The one-sentence description is far too sparse for that complexity, especially since it does not mention the required subsprint parameter or explain most optional fields.

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%, so the description must compensate for 12 undocumented parameters. It names title, description, code_locations, gates, and gate_timeout_ms, but leaves subsprint, dependencies, high_priority, agent_token, client_agent_id, claim_generation, client_session_id, and gate object fields 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?

The description states a specific verb and resource: 'Add an atomic item', and names the core required components. It is clear what the tool creates, but it does not differentiate this operation from sibling tools such as item_split or item_update.

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?

The description gives no explicit when-to-use or when-not-to-use guidance. It implies this is the creation path for atomic items, but it never names alternatives or explains when item_split, item_update, or other sibling tools are preferable.

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