Skip to main content
Glama

project_task_plan

Read-onlyIdempotent

Inspect a defined npm build, test, lint, typecheck, or check task without executing it, so you can review the planned command before running it.

Instructions

Inspect a defined npm build/test/lint task without executing it.

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": {
      "project_path": "<project_path>",
      "task": "<task>"
    },
    "name": "project_task_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYes
project_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered and the description's "without executing it" is consistent with it. The description adds no behavior beyond that — it does not say what inspection yields (resolved command, working directory, environment, what happens if the task is undefined).

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 tight sentence with the non-execution constraint front-loaded and no filler. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read-only tool with full annotations, the description is minimally adequate, but with no output schema the agent is left guessing what an "inspection" returns and what project_path must point at. Those gaps matter for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the burden for two required parameters. It mentions "build/test/lint" task names, but those are already enumerated in the schema, and it says nothing about project_path (format, resolution, whether a package.json is required at that location).

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?

The description pairs a specific verb ("Inspect") with a specific resource ("a defined npm build/test/lint task") and adds the key qualifier "without executing it," which implicitly separates it from project_task_run. It stops short of a 5 because it never names the contrasting sibling explicitly.

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?

"Without executing it" implies the when-to-use condition (preview/dry-run rather than run), which is real but indirect guidance. There is no explicit statement of when to prefer this over running the task, and no prerequisites or exclusions are given.

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