Skip to main content
Glama

輸入可請的假日天數

plan_leave_2027
Read-onlyIdempotent

輸入可請的假日天數,算出 2027 年最長的連休組合與要請哪幾天。

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": {
      "leave": "<leave>"
    },
    "name": "plan_leave_2027"
  }
}

Input Schema

NameRequiredDescriptionDefault
leaveYes可請天數 1~10

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety behavior is covered. Beyond that, the description only indicates that a result set consists of the longest combination plus which days to request; it says nothing about how weekends/holidays are treated or whether the result is a single best answer or ranked options. With annotations carrying the safety profile, a 3 is appropriate.

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?

One front-loaded sentence with zero filler; the input is mentioned first and the computed output second. It is efficient, though extremely terse, leaving room for a clause of routing context at little cost.

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

Completeness3/5

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

For a single-parameter, read-only computation with no output schema and full schema coverage, the description is minimally sufficient. It does not describe the shape of the returned plan or the assumptions behind 'longest', which an agent would want to set expectations for the user.

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?

With one parameter at 100% schema description coverage ('可請天數 1~10'), the schema already conveys meaning and range. The description restates the same concept in more natural wording but adds no syntax, unit, or edge-case guidance beyond the schema, so baseline 3 applies.

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 action (calculate) on a specific resource (2027's longest consecutive-holiday combinations and which days to request off), driven by an input of available leave days. An agent can tell this is an optimization/planning tool rather than a data lookup. It does not name or differentiate itself from the sibling get_2027_long_weekends, so it stops short of 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?

The intent is implied by the description: use it when you have a leave budget and want an optimal day-off plan. There is no explicit when-to-use, no stated prerequisite, and no pointer to the alternative get_2027_long_weekends for simpler enumeration queries. Adequate but leaves routing to inference.

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