Skip to main content
Glama
Sign In

Onplana

by io.github.Onplana
OverviewDiscussionsAdmin

decide_time_off

DestructiveIdempotent

Approve or decline a PENDING time off request. Requires org-wide project access (a manager). An approved request takes those working hours out of the capacity planner and tells the people running affected projects when it lands on tasks with little float; a declined one changes nothing. The person who asked is notified either way. A request already decided is refused with code NOT_PENDING.

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": {
      "timeOffId": "<timeOffId>",
      "status": "<status>"
    },
    "name": "decide_time_off"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
timeOffIdYesThe time off request id, as record_time_off returns it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description goes well beyond them: it explains the downstream consequence (hours removed from the capacity planner), the notification to project leads when float is thin, that declining is a no-op, that the requester is notified either way, and the exact error code for non-pending input. That is genuine operational context an agent cannot get from the annotations or schema.

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?

Four tight sentences, front-loaded with the action and eligibility, then consequences, then the error case. No sentence is filler; each carries a distinct fact the agent needs.

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?

No output schema exists, yet the description covers what the agent would otherwise lack: the authorization requirement, the capacity-planner side effect, notifications, the no-op decline, and the NOT_PENDING rejection. Nothing essential for a correct call 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 coverage is 50% — timeOffId is documented in the schema and status carries an APPROVED/REJECTED enum. The description reinforces 'PENDING' as the eligible state but adds no format or interpretation detail for either parameter beyond what the schema already conveys, so the baseline 3 applies.

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 pair ('Approve or decline') against a precisely scoped resource ('a PENDING time off request'), and the sibling set includes record_time_off, so the request-vs-decide split is unambiguous. An agent can tell instantly this is the decision tool, not the submission tool.

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?

Gives the precondition explicitly ('PENDING', 'Requires org-wide project access (a manager)') and the failure case ('A request already decided is refused with code NOT_PENDING'). It does not name record_time_off as the counterpart for creating requests, but the gating conditions are unambiguous.

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