Move a task to a different sprint. Specify the target sprint by number or ID.
| Name | Required | Description | Default |
|---|---|---|---|
| task_id | Yes | Task ID to move | |
| sprint_id | No | Target sprint ID (alternative to sprint_number) | |
| project_name | No | Project name (needed if using sprint_number) | |
| sprint_number | No | Target sprint number |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It doesn't disclose side effects, permission requirements, behavior when the target sprint is invalid, or reversibility. The description simply restates the action without additional behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, front-loaded with verb and object, no redundant words. It is appropriately sized for the simplicity of the operation.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations and no output schema, the description leaves behavioral aspects uncovered. It doesn't explain parameter interactions (e.g., needing project_name with sprint_number) beyond the schema, nor what happens on success or failure.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema descriptions already cover all parameters (100% coverage), so the description adds no significant new meaning. The phrase 'by number or ID' merely mirrors the existing sprint_number and sprint_id descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Move') and identifies the resource ('a task to a different sprint'), making the tool's function immediately clear and distinct from sibling tools like assign_task or update_task.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It implies the use case (moving a task between sprints) and hints at parameter selection ('by number or ID'), but doesn't explicitly state when to prefer this over alternatives or provide exclusions. The context is clear but lacks direct comparative guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct resource+action pairs (e.g., create_task vs update_task vs delete_task), but the large number of list/get/search tools creates some potential confusion, especially between get_context, search_entities, and find_documents. Descriptions are detailed and help, but the volume makes navigation less clear.
The majority of tools follow a consistent verb_noun pattern (create_, delete_, list_, update_, etc.), with clear prefixes like add/remove and link/unlink. Deviations like 'whoami', 'find_documents' vs 'search_entities', and 'setup_organization' prevent a perfect score.
62 tools is far beyond the typical MCP server scope and overwhelms agents with too many choices. Even if each tool is individually useful, the sheer count makes it difficult for an agent to efficiently select the right tool, increasing the likelihood of misselection.
The domain is well covered for projects, tasks, teams, sessions, and notifications, but there are notable gaps: no update_document, no get_task (only list/update/delete), no get_user, no reject_invite, and sprint management lacks update/delete operations. Core CRUD is present for many entities, but not all.
