Skip to main content
Glama

sprint_health

Check if your sprint is on track by analyzing completion rates, deadlines, and assignment health to get a verdict: on-track, at-risk, or off-track.

Instructions

Report whether a sprint is on track, in one call.

Composes project.task records for the sprint into completion %, deadline buckets (overdue / due today / upcoming / no deadline), assignment health, a per-stage and per-assignee breakdown, and a rule-based verdict.

Args: sprint_id: The project.task sprint_id to report on. project: Optional project-name filter (ilike). exclude_stages: Stage names dropped from sprint scope. Default ["Cancelled"]. done_stages: Stage names counted as completed. Default ["Done", "Delivered"]. lookahead_days: Days ahead that count as "upcoming" (default 7). timezone_offset: UTC offset for "today" (default 7 = Asia/Ho_Chi_Minh). subtasks_only: Count only subtasks (parent_id != False), the team's unit of work. Default True.

Note: sprint_id is a custom field, not standard Odoo; the tool degrades with a clear error when absent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNo
sprint_idYes
done_stagesNo
subtasks_onlyNo
exclude_stagesNo
lookahead_daysNo
timezone_offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses behavioral traits: composes task records into metrics and verdict, and degrades gracefully with error when sprint_id field absent. Covers key behaviors without contradiction.

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?

Description is well-structured with bullet list for parameters and clear opening sentence. While slightly long, each sentence contributes meaning and no wasted words. Front loads purpose effectively.

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?

Tool has output schema (not shown) but description already summarizes return components (completion %, deadlines, breakdown, verdict). With 7 params and complex logic, description covers essential context for correct invocation.

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

Parameters5/5

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

Input schema has 0% description coverage, but description explains each parameter in detail, including defaults, meaning, and contextual notes (e.g., sprint_id is custom field, subtasks_only default True). Adds substantial value beyond bare schema.

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?

Description clearly states the tool reports sprint health with specific verb 'report' and resource 'sprint health'. It distinguishes from siblings like project_status_report by focusing on sprint tracking.

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?

Description implies usage for checking sprint status in one call but does not explicitly state when to use or avoid compared to alternatives. No exclusions or contextual cues for sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/minhhq-a1/odoo-pulse'

If you have feedback or need assistance with the MCP directory API, please join our Discord server