Skip to main content
Glama

b24_scrum_sprint_list

Read-onlyIdempotent

Retrieve Scrum sprints for a group, filtered by status (active, planned, completed) with pagination support. Returns sprint IDs, names, dates, and status to manage sprint planning.

Instructions

List sprints of a Scrum group (tasks.api.scrum.sprint.list).

Returns a pagination envelope of sprint objects (id, name, dateStart, dateEnd, status, ...). Use the active sprint's id with b24_scrum_kanban_stages to get the real board columns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startNoPagination offset (page size is 50). Use 'next' from a prior response.
statusNoSprint status filter: 'active' (default), 'planned', 'completed', or null for all. Defaulting to 'active' avoids the pagination trap where the current sprint is never reached.active
group_idYesScrum group/project id (GROUP_ID).
fetch_allNoAuto-paginate and return all matching records (capped by BITRIX_MAX_PAGES, default 40 pages = 2000 records). Use a filter to keep this bounded.
webhook_urlNoOverride the default incoming webhook for this call (https://<portal>/rest/<user_id>/<token>/). If omitted, uses personal_webhook, then the X-B24-Webhook HTTP header, then the BITRIX_WEBHOOK_URL env default.
personal_webhookNoAct as a specific user (their personal incoming webhook). Takes precedence over webhook_url. Required to write to the portal under that user's permissions.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds return format details (pagination envelope of sprint objects with fields). No contradictions, and adds value beyond annotations.

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?

Two tightly written sentences plus a one-sentence hint. Every part is essential; no fluff. Front-loaded with action and resource.

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?

Given rich annotations, full schema coverage, and output schema existence, the description is sufficient. It covers the purpose, a key usage hint, and return shape. Minor omission: no mention of pagination behavior beyond 'pagination envelope', but schema covers start and fetch_all.

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

Parameters3/5

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

Input schema has 100% coverage with detailed descriptions for all 6 parameters. The description does not add further parameter-specific semantics. Baseline 3 is appropriate as schema fully documents parameters.

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?

Clearly states verb 'List' and resource 'sprints of a Scrum group', with API method reference. No ambiguity about what the tool does, and it is distinct from sibling tools (no other sprint-list tool).

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 a specific downstream usage hint (use active sprint id with b24_scrum_kanban_stages for board columns). Does not explicitly state when not to use or compare to alternative tools, but context is clear and actionable.

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/john7ross/BitrixMCP'

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