Skip to main content
Glama

Get the whole plan

get_plan

Retrieve the complete life plan as JSON, including values, goals, milestones, habits, decisions, logs, wins, and reviews to review or update the user's stored plan.

Instructions

Returns the full plan JSON (values, goals, milestones, habits, decisions, log, wins and reviews).

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": "get_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Returns' implies a read-only operation, but there is no note on payload size (a full plan with log, wins and reviews could be very large), whether data is ever trimmed or paginated, or permission/auth requirements. The section enumeration is the only behavioral disclosure.

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 front-loaded sentence with the verb and resource first and the payload contents in parentheses. Nothing is wasted and no sentence is redundant.

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?

With no output schema, the description must shoulder return-value explanation, and the section list does that at a high level. However, for a zero-param tool returning an entire data set, it omits practical details such as approximate payload size, JSON shape, or what happens when no plan exists.

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 nothing for the description to disambiguate; the baseline of 4 applies.

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 and resource ('Returns the full plan JSON') and enumerates the payload sections, so an agent knows exactly what resource it retrieves. It doesn't explicitly contrast itself with siblings like get_status or the per-section save_* tools, but the 'full plan' scope makes the distinction reasonably inferable.

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?

The description gives no when-to-use guidance, no prerequisites, and names no alternative. It never says whether to call this instead of assembling the plan from multiple section-specific tools, or when a narrower getter like get_status suffices.

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