Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

gws-mcp__calendar_freebusy

Read-only

Check availability (free/busy) for one or more people over a time range. Useful for finding open slots to schedule meetings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "time_min": "<time_min>",
      "time_max": "<time_max>",
      "emails": "<emails>"
    },
    "name": "gws-mcp__calendar_freebusy"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailsYesComma-separated email addresses to check availability for
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
time_maxYesEnd of the time range to check (ISO 8601)
time_minYesStart of the time range to check (ISO 8601)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description is consistent with a safe read. It adds the multi-person and time-range scoping context, but says nothing about what is returned (e.g., busy blocks per attendee) or how permissions/visibility affect results.

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?

Two short sentences, front-loaded with the core operation and with no filler. The second sentence is slightly soft ('Useful for...') but does carry scheduling intent rather than restating the name.

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?

A simple read-only lookup with full schema coverage and no output schema, so the description covers what an agent needs to invoke it. The only material omission is the shape of the response (busy intervals vs. free windows), which would help an agent interpret results.

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 coverage is 100%, so all four parameters are already documented, including ISO 8601 formats and the optional account selector. The description adds only the notion of querying multiple people at once, which the schema's 'comma-separated email addresses' already conveys.

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?

States a specific verb and resource ('Check availability (free/busy)') and clarifies scope ('one or more people over a time range'), so the operation is immediately understandable. However, it does not distinguish itself from the sibling gws-mcp__calendar_suggest_time, which plausibly overlaps in intent.

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 open slots to schedule meetings' gives an implied usage context, but there is no explicit when-to-use/when-not guidance and no named alternative. Given a sibling like calendar_suggest_time exists, the agent is left to infer which one to pick.

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

All DataToRAG 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