Skip to main content
Glama
Sign In

Onplana

by io.github.Onplana
OverviewDiscussionsAdmin

get_plan

Read-onlyIdempotent

Return a project's full plan tree in one call: project + epics + sprints + tasks (with parentId, epicId, sprintId, assignee, collaborators) + milestones. Optional includeDependencies adds each task's predecessor / successor edges; includeAgentBriefs adds the per-task brief. Capped at 500 tasks per response (taskTruncated=true if more exist - fall back to list_tasks for paginated reads). When the response carries taskTotal, that is the project's full task count, summary tasks included; summarize_project gives counts of work items for a large plan.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesProject id from list_projects.
includeAgentBriefsNoDefault false. When true, each task includes its agentBrief field.
includeDependenciesNoDefault false. When true, each task includes predecessors/successors arrays.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the 500-task response cap, the taskTruncated flag, and the meaning of taskTotal (including summary tasks). It also explains exactly what each optional flag adds to the payload, which the annotations do not cover.

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?

Front-loaded with the purpose and content list, then the flags, then the truncation caveat and fallback. Dense but every clause carries information; the taskTotal sentence is the only slightly awkward construction.

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

Completeness5/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 still tells the agent what the response contains, how large it can get, how truncation is signaled, and where to go for counts. Nothing essential for calling or interpreting the result is missing.

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%, so the defaults and effects of includeDependencies and includeAgentBriefs are already documented in the schema. The description restates those effects at a slightly higher level but adds no format or cost detail beyond the structured fields.

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

Purpose5/5

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

The description opens with a specific verb and resource ("Return a project's full plan tree in one call") and enumerates the exact contents (project, epics, sprints, tasks with key fields, milestones). That enumeration distinguishes it from get_project and get_epic, which return single entities.

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

Usage Guidelines4/5

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

It names two alternatives with the conditions that select them: list_tasks when the 500-task cap is hit, and summarize_project for counts on a large plan. It doesn't state when-not to use this tool at all (e.g., for a single task), so it falls just short of fully explicit routing.

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

All Onplana toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources