Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

plan_create

Create or replace a local project plan with up to 30 task steps and a defined goal, so the plan appears in the dashboard for tracking and resuming work.

Instructions

Create or replace a local project plan with up to 30 steps, visible in the dashboard.

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": {
      "goal": "<goal>",
      "steps": "<steps>"
    },
    "name": "plan_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesOverall project objective
stepsYesTask descriptions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write/scope profile is covered. The description adds that the operation is a replace (an overwrite of any existing plan), which is meaningful context beyond the annotations, but it says nothing about confirmation behavior, scope of 'local', or what is returned.

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?

A single front-loaded sentence with no filler; the verb, resource, limit, and visibility are all in the first clause. It is efficient, though slightly under-specified rather than padded.

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, no-output-schema tool with annotations present, the essentials are covered. Still missing is the replace semantics detail (does an existing plan get clobbered, and is the plan scoped to a project or the whole local workspace), which matters for an upsert-style write.

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 100% and the schema already documents 'goal' and 'steps' with the 1-30 item bound. The description's 'up to 30 steps' only restates maxItems, adding no new meaning such as step formatting or whether goal is a key/identifier.

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 pair ('create or replace') and resource ('local project plan'), plus a concrete constraint ('up to 30 steps') and an observable effect ('visible in the dashboard'). It does not explicitly distinguish itself from plan_update or plan_get, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance is given. The 'create or replace' phrasing hints at upsert behavior, but the description never says whether to prefer plan_update for edits or what happens if a plan already exists.

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