Skip to main content
Glama
Sign In

Onplana

by io.github.Onplana
OverviewDiscussionsAdmin

link_planner_plans

Idempotent

Link several Microsoft Planner plans into one Onplana portfolio in one call. Each plan becomes an Onplana project mirrored from Planner: its buckets, tasks, checklists and categories are imported, and the link keeps the project in step with Planner, read again every night (Sync now reads it at once). Every project lands in the portfolio named by portfolioName, which is found by name or created. A plan that already has a mirrored project is not imported again: it is added to the portfolio and linked if it was not, so a re-run creates no duplicates. At most 10 plans per call. A plan id is the Microsoft Graph plannerPlan id. Requires the Tasks and Groups permissions on the connected Microsoft account. Returns a result per plan with the project url, and the portfolio url.

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": {
      "planIds": "<planIds>",
      "portfolioName": "<portfolioName>"
    },
    "name": "link_planner_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
planIdsYesPlanner plan ids to link, 1 to 10.
portfolioNameYesThe portfolio the projects go into; found by name (case-insensitive) or created. 2 to 255 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations: it discloses what gets imported (buckets, tasks, checklists, categories), that the link is kept in step by a nightly sync with an immediate 'Sync now' option, the 10-plan call cap, the required Tasks and Groups permissions, and the dedupe behavior on re-run. These are exactly the operational facts an agent needs before committing a write.

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 action and resource, then layered detail on import, sync, dedupe, limits, permissions, and returns. Dense but every sentence carries information; the parenthetical '(Sync now reads it at once)' is slightly awkward phrasing but not wasteful.

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?

For a two-parameter write tool with no output schema, the description covers the import payload, idempotency, throttling limit, auth requirements, and even the return shape ('a result per plan with the project url, and the portfolio url'). Nothing material is left for the agent to guess.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond it: planIds are Microsoft Graph plannerPlan ids (a specific external identifier format), and portfolioName is resolved case-insensitively or created. That clarifies resolution semantics the schema only restates.

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?

States a specific verb and resource: 'Link several Microsoft Planner plans into one Onplana portfolio in one call', naming both the source system (Planner) and the target container (Onplana portfolio). This clearly separates it from siblings like add_project_to_portfolio (single existing project) and preview_migration (no commit), so an agent can pick it without opening the schema.

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?

Explains the batch-link use case and the re-run semantics ('a plan that already has a mirrored project is not imported again... a re-run creates no duplicates'), which tells the agent it is safe to retry. It does not explicitly name an alternative tool for linking a single plan versus many, so it stops short of full when-not guidance.

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