Skip to main content
Glama

plan_leave

Read-onlyIdempotent

Föreslå fördelning av kvarvarande föräldradagar (av 480: 390 sjukpenningnivå + 90 lägstanivå) mellan 1–2 föräldrar med schema, datum och belopp. Motiverar fördelningen (reserverade vs överlåtbara dagar, dubbeldagar först). Förtydligar att grundnivå (250 kr/dag) är golvet för sjukpenningnivå medan lägstanivå (180 kr/dag) är en egen dagtyp – de är inte samma sak. Om barnet redan är fött startar planen idag och uttagna dagar räknas bort. Returnerar alltid planera_har (produktions-URL till planeraren) och källa.

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": {
      "foraldrar": "<foraldrar>",
      "fodelsedatum": "<fodelsedatum>"
    },
    "name": "plan_leave"
  }
}

Input Schema

NameRequiredDescriptionDefault
idagNoValfritt dagens datum ÅÅÅÅ-MM-DD
onskemalNo
foraldrarYes
startdatumNoValfritt startdatum ÅÅÅÅ-MM-DD (standard: födseln, eller idag om barnet redan är fött)
fodelsedatumYesBarnets (beräknade) födelsedatum, ÅÅÅÅ-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / foraldrar / items / properties / uttagna
      Added value: +{
      +  "description": "Redan uttagna dagar för förälderns del",
      +  "properties": {
      +    "lagstaniva": {
      +      "type": "number"
      +    },
      +    "sjukpenningniva": {
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / idag
      Added value: +{
      +  "description": "Valfritt dagens datum ÅÅÅÅ-MM-DD",
      +  "type": "string"
      +}
    • addedInput schema / properties / onskemal / properties / dubbeldagar
      Added value: +{
      +  "description": "Antal dubbeldagar att lägga först (max 60, före 15 månader)",
      +  "type": "number"
      +}
    • addedInput schema / properties / startdatum
      Added value: +{
      +  "description": "Valfritt startdatum ÅÅÅÅ-MM-DD (standard: födseln, eller idag om barnet redan är fött)",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavior beyond that: it justifies the proposed split (reserved vs transferable days, double days first), deducts already-taken days when the child is born, and commits to always returning planera_har and källa. That is meaningful disclosure the annotations cannot 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 action and scope are front-loaded in the first sentence, followed by justification behavior, then domain clarification and the return contract. Every sentence carries information, though the grundnivå-vs-lägstanivå clarification is the least essential and the paragraph runs long for a single description. It remains dense rather than padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly states what is always returned (planera_har and källa). It also covers the start-date default, the already-born edge case, and the domain day model, which is enough for a nested-input planning tool. Minor gaps remain around how schedule inputs (dagar_per_vecka, andel_forsta_foraldern) influence the output, but nothing critical 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 60%, leaving gaps such as dagar_per_vecka and the pay-level distinction undocumented in the schema. The description compensates by explaining the day budget (480 = 390 sjukpenningnivå + 90 lägstanivå), that dubbeldagar are laid first, and that grundnivå (250 kr) is a floor within sjukpenningnivå while lägstanivå (180 kr) is a separate day type. It also restates the start-date default, adding domain meaning the raw fields lack.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: it proposes a distribution of remaining parental days (390 sick-pay level + 90 minimum level of 480) across 1-2 parents, with schedule, dates and amounts. That is far more concrete than the bare name 'plan_leave'. It does not explicitly name any sibling such as calc_benefit or days_remaining to draw the boundary, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by the planning framing and the conditional 'if the child is already born, the plan starts today and taken days are deducted', which tells the agent about an edge case. However, there is no explicit statement of when to choose this over calc_benefit, days_remaining, or explain_rule, and no exclusion criteria. The agent must infer the routing from the verb alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources