Skip to main content
Glama
AIOProductOS

AIOProductOS

Official
by AIOProductOS
OverviewSchemaSourceRelated ServersDiscussions(2)Admin
JavaScript
Remote

Create Sprint

create_sprint

Create a sprint with a name and optional goal, state, and ISO dates, then receive its id and details. Use the returned id to schedule tasks by passing it as sprint_id on create_task or update_task.

Instructions

Create a sprint and return it (id, name, goal, state, dates). state is 'future' (default) or 'active'; start_date / end_date are optional ISO 8601. Only name is required. Schedule tasks into it by passing the returned sprint id as sprint_id on create_task / update_task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNoThe sprint goal (optional).
nameYesSprint name (the only required field), e.g. 'Sprint 12'.
stateNoLifecycle state (optional; default 'future').
end_dateNoEnd, ISO 8601 (optional).
start_dateNoStart, ISO 8601 e.g. '2026-07-15T00:00:00Z' (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.14
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / examples
      Added value: +[
+  {
+    "goal": "Ship SSO",
+    "name": "Sprint 12",
+    "state": "active"
+  }
+]
  2. Addedv0.1.6

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only indicate no read-only/destructive/idempotent behavior, leaving the description to explain the operation. The description discloses the return payload, default state ('future'), optional dates, and the fact that only name is required. This goes beyond annotations, though it does not mention permissions or validation error behavior.

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 concise sentences deliver purpose, key parameter behavior, and downstream usage with no redundant wording. The description is front-loaded with the main action and each sentence adds necessary information.

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?

Completes the picture for a create tool: describes return value, optional fields, defaults, and how to integrate with create_task/update_task. No output schema exists, and the description covers the essentials. It doesn't discuss error cases or permissions, but these are less critical for a straightforward create operation with good schema annotations.

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

Parameters4/5

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

Schema covers all 5 parameters at 100%, providing baseline. The description adds value by specifying state default ('future'), date format (ISO 8601), and emphasises that only name is required. This clarifies optionality beyond the schema's 'required' field.

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 a specific action, 'Create a sprint and return it', with a clear resource and output. The description distinguishes this from sibling tools like update_sprint by focusing on creation and including the returned sprint id for task scheduling, which is unique to create_sprint.

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

Usage Guidelines4/5

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

Provides clear intended use: create a sprint with required name and optional fields, then use the returned id to schedule tasks. It explains the workflow downstream, but does not explicitly contrast with update_sprint or list_sprints, so a small exclusion hint is missing.

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