Skip to main content
Glama

Ganty MCP

by app.ganty

reschedule_and_propagate

Compute the downstream impact of shifting a single task. Default is dry_run (no DB writes); set mode='commit' to actually persist the changes. Cascades forward only (no pull): successors are pushed only if their predecessor's new end + lag would violate their current start. Tasks with progress=100 are treated as pinned; pass pinned_task_ids for additional pins. When a pin would be violated, the change is recorded in 'conflicts' and not propagated further. In mode='commit', if any conflicts exist nothing is written (all-or-nothing transaction). Same v1 limitations as get_critical_path: FS only, calendar days by default, no holiday table, ignores multi-period segments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNodry_run (default): compute and return; do not modify DB. commit: write to DB in a single transaction, but only if no conflicts. Audit logged on commit.
shiftNoRelative shift like '+3d' (push back) or '-2d' (pull earlier). Specify exactly one of shift or new_start_date.
task_idYesTask ID (UUID) to shift
business_daysNoIf true, skip Sat/Sun in duration math. Defaults to false.
new_start_dateNoAbsolute new start date as YYYY-MM-DD. Specify exactly one of shift or new_start_date.
pinned_task_idsNoAdditional task IDs to treat as pinned (in addition to progress=100 tasks).
respect_dependenciesNoIf false, only the named task moves; successors are not cascaded. Default true.

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries full burden and excels: it discloses default dry_run (no DB writes), commit mode with all-or-nothing transaction, forward-only cascading, pinned tasks (progress=100 plus additional), conflict recording and propagation stopping, and known v1 limitations. This is exceptional behavioral transparency.

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?

The description is dense but well-structured: first sentence states core purpose and mode, second explains propagation rules, third covers limitations. It is slightly long but every sentence contributes critical information for a complex tool. Front-loading the purpose and default behavior is effective.

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 the 7-parameter complexity, no output schema, and no annotations, the description is nearly complete. It covers modes, conflict handling, pinned tasks, and limitations. The only minor gap is a lack of explicit return-value description, but the commit/dry_run distinction implies what is returned. Referencing get_critical_path for limitations is efficient.

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?

Schema coverage is 100%, so baseline is 3. The description adds context about shift behavior (e.g., 'pushes only if predecessor's new end + lag would violate'), but most parameter semantics are already in the schema. The description repeats some schema details (mode, pins) without adding significant new meaning beyond behavioral context.

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?

The description opens with a specific verb+resource: "Compute the downstream impact of shifting a single task." It clearly distinguishes itself from generic update tools by focusing on propagation and impact analysis. The title and sibling context further reinforce its specialized role.

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?

The description implies usage context by explaining the dry-run default (for planning) and commit mode (for persistence), and by referencing get_critical_path for shared limitations. It does not explicitly name alternatives or state when not to use, but the clear purpose and mode semantics give sufficient guidance for an agent.

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

All Ganty MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool targets a distinct resource-action pair, such as create_task vs update_task vs set_task_progress. Even the two task-modifying tools have clearly separated concerns: one updates arbitrary fields, the other specifically updates progress with auto-derived status.

Naming Consistency5/5

All tool names follow the verb_noun snake_case pattern (create_, list_, delete_, get_, add_, set_, update_). The only compound verb, reschedule_and_propagate, still fits the pattern and reads predictably.

Tool Count5/5

15 tools is within the well-scoped 3-15 range, and each tool covers a meaningful operation for a project management domain. No redundant or trivial tools are present.

Completeness3/5

Tasks have full CRUD plus progress and dependency management, but milestones lack update/delete operations, and dependencies only support addition (no removal). These are notable gaps that may require workarounds in some workflows.

Resources