Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

calendar_check_availability

Read-onlyIdempotent

Check when you have free time in Google Calendar. Shows busy periods and free slots in a given time range. Useful for finding meeting times or checking schedule conflicts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_timeNoEnd date/time to check availability (YYYY-MM-DD or ISO 8601). Defaults to end of start_time day, or 7 days from now.
timezoneNoIANA timezone (e.g. 'Asia/Bishkek') that start_time/end_time WITHOUT an offset are in, and that the free slots are reported in. OMIT for UTC.
start_timeNoStart date/time to check availability (YYYY-MM-DD or ISO 8601). Defaults to start of today.
calendar_idNoCalendar ID to check. OMIT to use the agent's configured default calendar (or primary).
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
working_hours_onlyNoIf true, only show free slots during working hours (9 AM - 6 PM). OMIT to show all free time (the default).
min_duration_minutesNoMinimum duration in minutes for free slots. Filters out short gaps. Default: 30 minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / timezone
      Added value: +{
+  "description": "IANA timezone (e.g. 'Asia/Bishkek') that start_time/end_time WITHOUT an offset are in, and that the free slots are reported in. OMIT for UTC.",
+  "type": "string"
+}
  3. Added
  4. Removed
  5. Changed2 schema fields changed
    • removedInput schema / properties / calendar_id / default
      Removed value: -"primary"
    • changedInput schema / properties / calendar_id / description
      Previous value: -"Calendar ID to check. Defaults to primary calendar."New value: +"Calendar ID to check. OMIT to use the agent's configured default calendar (or primary)."
  6. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds what the result contains ('busy periods and free slots'), but says nothing about auth requirements, rate limits, or pagination. With annotation coverage, 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?

Three short sentences, front-loaded with the core action. Slight redundancy between 'check when you have free time' and 'shows busy periods and free slots' keeps it from a 5, but nothing is wasted.

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

Completeness5/5

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

For a read-only query tool with seven fully documented optional parameters and no output schema, the description covers purpose, output nature, and use case adequately. Nothing an agent needs to invoke it correctly is missing.

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 defaults, timezone format, and omission semantics all documented in the schema itself. The description adds no parameter-level meaning, so the 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 uses a specific verb+resource ('Check ... free time in Google Calendar') and clarifies the return shape ('busy periods and free slots'), which distinguishes it from calendar_list_events. It stops short of naming a sibling tool explicitly, so it loses the top score.

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?

'Useful for finding meeting times or checking schedule conflicts' gives implicit usage context, but there is no explicit when-to-use vs. when-not and no routing to alternatives such as calendar_list_events or calendar_create_event.

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

All dialogbrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources