Skip to main content
Glama
Sign In
freispace MCP Server

freispace MCP Server

Official
by freispace
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_staff_next_holiday

Retrieve the next upcoming holiday for a staff member: start date, end date, duration in days, and comment. Omit staff name to see your own.

Instructions

Get a staff member's next upcoming holiday: start date, end date, length in days and comment. Omit staff_name to get the calling user's own next holiday.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_staff_next_holiday"
  }
}

Input Schema

NameRequiredDescriptionDefault
staff_nameNoStaff member name. Partial names match; the first match is used. Omit for the calling user's own staff record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses returned fields but omits details on error handling (e.g., staff not found, no upcoming holiday), side effects, or authentication requirements. Adequate but not thorough.

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?

Two sentences with no filler. Front-loaded with output fields, then optional parameter behavior. Every word earns its place.

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?

Describes return value fields and optional parameter. However, lacks edge-case behavior (e.g., no upcoming holiday returns null/empty). In a suite of many sibling tools, it provides clear distinction.

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 covers 100% and description adds significant value: explains partial name matching, first match rule, and omit-for-self behavior. Schema alone only gives parameter name and type.

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?

Description uses specific verb 'Get' and resource 'staff member's next upcoming holiday,' listing exact output fields (start date, end date, length, comment). Clearly distinguishes from siblings like get_staff_holiday_quota.

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?

States when to omit staff_name for self-service, but lacks explicit guidance on when to prefer this tool over alternatives (e.g., get_availability). Usage context is implied but not fully explained.

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

Deploy Server

Other Tools