Skip to main content
Glama
garoon
by garoon

Get Schedule Events

garoon-get-schedule-events
Read-only

Retrieve schedule events within a specified date range from Garoon, filtering by user, organization, or facility, with options for private events and pagination.

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
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, establishing the read-only safety profile. The description adds the period-based search scope but does not mention pagination, private-event handling, or target-type implications, though it does not contradict the annotations.

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?

The description is a single sentence that immediately states the action and scope with no filler or redundant detail. It is concise and front-loaded.

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?

The schema and output schema provide strong parameter and result context, and annotations cover safety. However, the description lacks sibling differentiation and does not highlight relevant behavioral nuances, leaving some contextual gaps for an agent choosing among schedule-related tools.

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%, with rich detail for all 7 parameters including defaults, enum values, and the GAROON_PUBLIC_ONLY override behavior. The description itself adds no parameter semantics, so the baseline score of 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 uses a specific verb ('Search') and resource ('schedule events') with a specified period, clearly indicating the tool's core function. It does not explicitly differentiate this from the sibling tool 'garoon-search-available-times', which is also schedule-related.

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 guidance is provided on when to use this tool versus alternatives such as 'garoon-search-available-times' or 'garoon-create-schedule-event'. The description only states the basic action, leaving the agent to infer usage context from the sibling list.

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