Skip to main content
Glama
Sign In

Onplana

by io.github.Onplana
OverviewDiscussionsAdmin

update_closeout_lessons

DestructiveIdempotent

Record a project's lessons learned on its closeout while it is DRAFT. values maps a lesson key to its text: wentWell, toImprove, scheduleVarianceReason, budgetVarianceReason and leavesBehind (impacts that continue after handover and who inherits each). Null or an empty string clears a lesson; keys not sent keep their answer. The organization may label the keys differently; get_closeout_status returns the labels. Refused before the closeout is started (CLOSEOUT_NOT_FOUND) and once it is in review or signed off (CLOSEOUT_LOCKED). Needs project.edit. Returns the record get_closeout_status returns.

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>",
      "values": "<values>"
    },
    "name": "update_closeout_lessons"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A5/5.0
Behavior5/5

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

Adds a lot beyond the annotations: null/empty string clears a lesson (matching destructiveHint=true), unsent keys are preserved (patch semantics), the permission requirement, the precise error gating, and a return-value reference. The destructive and idempotent hints are explained rather than merely declared.

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?

Dense but front-loaded: purpose and state constraint lead, followed by the key semantics, then clearing/patch behavior, then gating/errors. Every sentence contributes distinct, actionable information with no padding.

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, it still tells the agent the return value ('the record get_closeout_status returns'). Combined with permission, state gating, and error codes, an agent has everything needed to call it correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does: it names every lesson key with its meaning, explains that null/empty clears and omitted keys persist, and notes that orgs may relabel the keys. Only projectId goes unremarked, which is self-evident from the closeout context.

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?

Specific verb (Record) plus resource (a project's lessons learned on its closeout) and a state constraint (while DRAFT). It is immediately distinguishable from sibling closeout tools like initiate_closeout, get_closeout_status, and submit/decide_closeout_signoff.

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?

Explicitly states the usable state (DRAFT), the two refusal conditions with error codes (CLOSEOUT_NOT_FOUND before start, CLOSEOUT_LOCKED in review/signed off), the required permission (project.edit), and points to get_closeout_status for org-specific key labels.

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