Conecto

Approve, decline or cancel leave

hr_decide_leave

Decide on a leave request: approve or decline one that is pending, or cancel one that is pending or approved (approved days go back to the balance). Declined and cancelled requests stay as they are; ask again with hr_request_leave. Approving checks the balance again; allow_negative: true lets it go below 0. Returns the request and the balance after it. Costs $0.01 per call; nothing if it fails.

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": {
      "request_id": "<request_id>",
      "decision": "<decision>"
    },
    "name": "hr_decide_leave"
  }
}

Input Schema

Name	Required	Description	Default
`note`	No
`decision`	Yes
`request_id`	Yes
`allow_negative`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The annotations only give generic hints (not read-only, not destructive, not idempotent). The description adds real behavioral context beyond them: approving re-checks the balance, allow_negative permits negative balances, approved days are returned to the balance on cancel, and the call costs $0.01 with no charge on failure.

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 dense sentences with no filler: preconditions, sibling hand-off, balance behavior, return value and cost, in that order. Everything is front-loaded and each clause carries information an agent needs before calling.

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?

There is no output schema, so the description's 'Returns the request and the balance after it' is necessary and sufficient. Combined with the state preconditions and pricing note, nothing an agent needs to invoke this mutation correctly is missing.

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 0%, so the description must carry the load, and it does for the two decision-critical parameters: the approve/decline/cancel enum and allow_negative are both explained with their effects. The `note` parameter and `request_id` are left unaddressed, a small remaining gap.

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?

Opens with a specific verb+resource ('Decide on a leave request') and immediately enumerates the three decision modes with their required states. An agent can distinguish it from hr_request_leave and hr_adjust_leave 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 Guidelines5/5

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

Explicitly gates each decision on request state (approve/decline only when pending; cancel when pending or approved) and names hr_request_leave as the follow-up path, since declined/cancelled requests 'stay as they are'. Both when-to-use and the alternative are stated.

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

All Conecto 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.

Resources

Need Help?