Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

plan_get

Read-only

Retrieves the saved task plan so you can review current progress and resume work from the persisted checkpoint.

Instructions

Read the current persisted task plan.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "plan_get"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds modest value with "persisted" and "current", signalling that this returns stored state rather than an in-memory draft, but it does not say what happens when no plan exists (empty result vs. error), which is the one behavior an agent would actually worry about here.

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 seven-word sentence with no filler, and the resource is front-loaded after the verb. It is efficient rather than padded, though the extreme brevity leaves the usage and empty-state gaps noted elsewhere.

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 zero-parameter read with full annotation coverage and no output schema, the description covers what the tool does and that the result is persisted state. The only meaningful omission is the empty/no-plan case, which is a small gap given the tool's simplicity.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics for the description to carry; baseline is 4. Nothing in the description misleads about inputs, and additionalProperties=false reinforces that no arguments are expected.

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 names a specific verb ("Read") and a specific resource ("the current persisted task plan"), which is unambiguous. It implicitly distinguishes itself from the write-oriented siblings plan_create and plan_update, but never names them or states the contrast explicitly, so it stops short of a 5.

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 only implied by the verb "Read": an agent can infer this is the retrieval counterpart to plan_create/plan_update. There is no explicit when-to-use statement, no guidance on when to re-read vs. rely on a cached plan, and no exclusion of alternatives.

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