Skip to main content
Glama

Project Critical Path

bpj_schedule_critical_path
Read-onlyIdempotent

Compute the earliest schedule, project duration, and slack for up to 60 tasks with finish-to-start dependencies.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tasks": "<tasks>"
    },
    "name": "bpj_schedule_critical_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
tasksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, closed-world, non-destructive computation, so the safety burden is off the description. The description adds the 60-task ceiling and the finish-to-start-only constraint, which are real behavioral limits. It is silent on what happens with cyclic graphs, unknown predecessor IDs, or over-limit input, which matters for a solver-like tool.

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?

A single sentence with no filler, front-loading the verb and the three return values, then the operating limits. Nothing to trim.

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?

For a one-parameter, no-output-schema tool with rich read-only annotations, the description covers what is computed and the input bounds. The main residual gap is failure behavior on malformed or cyclic input, which an agent would need to call it confidently.

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 description coverage is 0%, so the description should compensate, and it only partly does: it clarifies the 60-task maximum and that dependencies are finish-to-start, which gives meaning to the predecessor IDs. It does not explain the pipe-delimited line format or units, though the property title does carry that format string.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Compute") and the three concrete outputs (earliest schedule, project duration, slack), plus the dependency model and task cap. An agent knows exactly what it gets back. It does not distinguish from any sibling, but the sibling list is a set of unrelated single-purpose utilities, so differentiation is less critical here.

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?

Usage is implied by the scope constraints: finish-to-start dependencies only, max 60 tasks. That implicitly excludes other dependency types and larger networks, but there is no explicit "use this when…" statement and no named alternative for related scheduling needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.