Skip to main content
Glama
garoon
by garoon

Get Schedule Events

garoon-get-schedule-events

Retrieve Garoon schedule events for a specified target and date range. Control privacy, limit, and offset for targeted results.

Instructions

Search for schedule events in a specified period in Garoon

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of events to return (1-1000, default: 100 - server default)
offsetNoStarting position for results (0 or greater, default: 0 - server default)
targetYesTarget ID as a numeric string (e.g., 12345) - user ID, organization ID, or facility ID
rangeEndYesEnd datetime of the search range in RFC 3339 format (e.g., 2024-01-07T23:59:59+09:00). Must be after rangeStart
rangeStartYesStart datetime of the search range in RFC 3339 format (e.g., 2024-01-01T00:00:00+09:00). Must be before rangeEnd
targetTypeNoType of target: 'user', 'organization', or 'facility' (default: 'user')user
showPrivateNoWhether to include private events in the search results. When true, includes both public and private events. When false, only public events are returned. NOTE: If GAROON_PUBLIC_ONLY is set to 'true', this parameter will be automatically overridden to false and only public events will be returned, regardless of the value specified

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message. Present on error
resultNoResult of the operation. Present on success
statusNoHTTP status code from the Garoon API. Present only when the error is an HTTP error response
responseTextNoRaw response body from the Garoon API. Present only when the error is an HTTP error response
Behavior2/5

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

With no annotations present, the description must fully disclose behavioral traits. It only mentions searching in a period, but omits details such as read-only nature, data limit, pagination, or authentication requirements. The description adds minimal behavioral context beyond the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one sentence, which is concise but lacks structure. It provides no breakdown of key aspects like target types or private events. It is not overly wordy, but could be more informative without sacrificing conciseness.

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

Completeness2/5

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

Given the tool has 7 parameters (3 required) and an output schema, the description is too sparse. It does not mention critical details such as the role of 'target' and 'targetType', the 'showPrivate' parameter behavior, or the default values. The description leaves the agent to infer too much from the schema alone.

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?

The schema covers 100% of parameters, so the description does not need to add meaning beyond the schema. The description does not elaborate on any parameter, which is acceptable since the schema itself is detailed. Baseline score of 3 is appropriate.

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 clearly states the action ('Search for schedule events') and the context ('in a specified period in Garoon'). It is specific enough to distinguish from sibling tools like 'garoon-create-schedule-event' or 'garoon-get-bulletin-topics'. However, it could more explicitly contrast with other get/search tools.

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

Usage Guidelines2/5

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

No guidelines are provided about when to use this tool versus alternatives. For example, there is no mention that this tool is for date-range searches, while 'garoon-search-available-times' might be for availability checks. The description lacks any usage context or preconditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/garoon/garoon-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server