Skip to main content
Glama
Sign In
freispace MCP Server

freispace MCP Server

Official
by freispace
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_my_schedule

Retrieve your upcoming bookings within a specified date window. Defaults to the next 7 days for a quick overview.

Instructions

The calling user's own bookings in a date window (default: the next 7 days). Use it for questions like 'what is on my schedule this week'.

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_my_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoWindow end, YYYY-MM-DD (inclusive).
daysNoWindow ends this many days after start, inclusive (alternative to 'to'). Default 7.
fromNoWindow start, YYYY-MM-DD. Default today.
weeksNoWindow length in weeks (overrides 'days').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/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. Describes read operation (calling user's own bookings) and default window (next 7 days). Does not specify whether past bookings are included or other behavioral details like cancellation status. Adequate but could be more explicit about the forward-looking nature.

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, front-loaded with the main action. No redundant information. Every sentence 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?

Given 4 optional parameters (all described in schema) and no output schema, the description is complete enough for a simple read tool. It explains what it does and when to use it. Could mention return type (list of bookings), but not essential.

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 description coverage is 100%, baseline 3. Description adds minimal extra beyond schema: it mentions default window and provides a usage example but does not clarify parameter interactions or constraints beyond schema definitions.

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 clearly states verb ('get'), resource ('user's own bookings'), and scope ('in a date window'). Distinguishes from siblings by specifying 'calling user's own bookings', making it unique among tools like get_staff_collaborators or get_my_tasks.

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?

Explicitly says when to use it: for questions like 'what is on my schedule this week'. Implies context (user's own schedule) but does not explicitly exclude alternatives or mention when not to use. However, the context is clear from the description and sibling tool names.

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