Onplana

get_project

Read-onlyIdempotent

Get full detail on one project (team, milestones, task counts) by id. Use this after list_projects to resolve a name → id and pull enough context to reason about the project without a follow-up call. The caller can only see projects they own, are a member of, or have org-admin visibility for - out-of-scope ids return not_found. PREFER get_plan when you need the FULL task tree (epics + sprints + tasks + deps + milestones in one call); this tool returns only headline data. autoSchedule false means the project has automatic scheduling off: an edit or a new link moves no other task until someone presses Recalculate. parentDatesFromSubtasks true means a task with subtasks takes its dates from them unless the task says otherwise (each task reports datesFromSubtasks). retainedLogic true means the remaining work of a started task waits on its links, so a late predecessor pushes it; false means a started task holds. archivedAt set means the project is archived and read-only: every write to it is refused (PROJECT_ARCHIVED) until it is unarchived. When taskCounts carries summaryTasks, the other counts are work items (tasks with no subtasks) and summaryTasks is the number of summary tasks, such as phases, they leave out. scheduleRisk, when present, is the latest finished schedule risk run: p80 is the date the project finishes by in 80 percent of simulated outcomes, chance (0 to 1) is the likelihood of finishing by against, which is the target date (chanceOf target) or the plan finish (chanceOf plan), and runAt is when the run finished. It is absent when the project has no finished run or the plan does not include schedule risk.

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_project"
  }
}

Input Schema

Name	Required	Description	Default
`projectId`	Yes	Project id from list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

AddedJun 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The annotations already declare this as a safe, read-only, idempotent, closed operation, but the description adds substantial context beyond them. It discloses visibility rules, the not_found behavior for out-of-scope ids, the read-only effect of archivedAt, and the meanings of several project flags and scheduleRisk. This gives the agent behaviorally useful information that the annotations alone do not provide.

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?

The description is front-loaded with purpose, workflow, permissions, and the main get_plan alternative before turning to field semantics. It is lengthy, but most of the length is justified because there is no output schema and the field meanings would otherwise be opaque. There is some density and repetition around return detail, but no clearly wasted sentence.

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?

Given that the tool is a read-only detail fetch with one required parameter and no output schema, the description is unusually complete. It explains what is returned, how visibility affects results, what archivedAt means, and how several fields should be interpreted. The agent has enough context to call the tool correctly and reason about the result without an additional metadata lookup.

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 only parameter is projectId, which is already documented in the schema as coming from list_projects. The description reinforces the workflow of resolving a name to an id, but it adds no additional parameter syntax, format, or constraints beyond the schema. A baseline score of 3 is appropriate when the schema already fully documents the parameters.

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 states a specific verb and resource: get full detail on one project by id. It immediately distinguishes this tool from get_plan by saying get_project returns headline data while get_plan returns the full task tree, so an agent can choose between them without opening either schema.

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

Usage Guidelines5/5

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

It gives explicit workflow guidance: use this after list_projects to resolve a name to an id and pull enough context without a follow-up call. It also names the alternative get_plan and the condition when that alternative is preferred. Permission scope and out-of-scope behavior are stated as well.

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

All Onplana tools Inspect

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.