A
licenseNot graded
qualityA
maintenancewhen2meet-style scheduling polls — self-hostable, reverse-proxy-auth friendly, agent-first API (OpenAPI + llms.txt + MCP).
MIT
meetwhen
Server Details
Free no-signup group scheduling (a modern When2meet): share one link, find a time for everyone.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.3/5.0
Tool DescriptionsA
Average 4.4/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation5/5
The two tools have clearly distinct purposes: create_event generates a new event, while get_event retrieves event details. No functional overlap exists.
Naming Consistency5/5
Both tools follow the consistent 'verb_noun' pattern (create_event, get_event), making them predictable and easy to use.
Tool Count3/5
With only 2 tools, the set feels minimal but not unreasonable for a simple polling service. It is on the low end of the typical 3-15 range.
Completeness4/5
The tools cover the core workflow of creating and viewing events, but lack update and delete functionality, which are minor gaps for a poll-like service.
Available Tools
2 toolscreate_eventAInspect
Create a free, no-signup group-scheduling event (like When2meet) and get a shareable link. Give it candidate dates and a daily time window; it builds the availability grid. Send the returned url to everyone in the group — each person paints when they're free in their own timezone, and the best overlapping time surfaces automatically. Ideal when a user asks you to 'find a time' or 'set up a poll' for a meeting.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | 'time' (default): find an overlapping hour within a daily window. 'day': a whole-day poll — respondents just mark which dates work, no time-of-day. Use 'day' when the user only needs to pick a date. | |
| dates | Yes | Candidate dates as YYYY-MM-DD strings (1-21 days). | |
| title | Yes | Event name, e.g. 'Team sync' or 'D&D night' (max 80 chars). | |
| timezone | No | IANA timezone the hours are expressed in, e.g. 'America/New_York' (default UTC). Respondents still answer in their own local time. | |
| latest_hour | No | Latest hour of day to consider, 1-24 (default 17). Must be greater than earliest_hour. | |
| slot_minutes | No | Granularity of each time slot in minutes (default 30). | |
| earliest_hour | No | Earliest hour of day to consider, 0-23 (default 9). Ignored when mode='day'. |
Tool Definition Quality
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It details the flow: give dates and time window, the system builds an availability grid, returns a URL, respondents mark availability in their own timezone, and the best time emerges. It also explains timezone and mode behaviors. No contradictions.
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?
The description is well-structured in two paragraphs, with a clear first sentence. It is slightly verbose but remains focused. Every sentence serves a purpose. Could be tightened, but it is easy to read and informative.
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?
Given the lack of output schema, the description adequately covers the return value as a 'shareable link' or 'returned url'. It explains the overall process, prerequisites (candidate dates and time window), and the outcome. It is complete for the tool's complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. The description adds value by providing usage context for parameters (e.g., when to use 'day' mode vs 'time', default values for earliest_hour and latest_hour, and that respondents answer in their local time). It enhances understanding beyond the schema descriptions.
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?
The description clearly states the tool creates a free, no-signup group-scheduling event similar to When2meet and provides a shareable link. It specifies the action (create), the resource (event), and the outcome (shareable link). The sibling tool get_event suggests retrieval, distinguishing this tool as creation.
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?
The description explicitly states it is 'ideal when a user asks you to find a time or set up a poll for a meeting,' providing clear usage context. It also differentiates between 'time' and 'day' modes. However, it does not explicitly state when not to use the tool or mention alternatives beyond the sibling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_eventAInspect
Read the current state of a meetwhen event: how many people responded, who, and the best overlapping time(s) so far. Use the event id returned by create_event (or found in a meetwhen /e/ URL).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| event_id | Yes | The event id returned by create_event. | |
| timezone | No | IANA timezone to render the best-time labels in (default UTC). |
Tool Definition Quality
A4.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must fully disclose behavior. It indicates a read operation but lacks details on error cases (e.g., invalid event_id) or side effects. The statement 'current state' implies dynamism but could be more explicit.
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 two sentences, front-loaded with the primary purpose, and includes a practical usage note. No unnecessary words or repetition.
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?
For a simple read tool with no output schema, the description covers core outputs and event_id sourcing. It doesn't detail the exact response structure, but the mention of 'how many, who, best times' is sufficient for a basic understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for both parameters. The description adds value by explaining the event_id originates from create_event or a URL, which enhances understanding beyond the schema.
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?
The description clearly states the tool reads the current state of a meetwhen event, listing specific outputs (responses, people, best times). It distinguishes itself from the sibling create_event by being a read operation.
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?
The description instructs when to use the tool (after creating an event or from a URL), but doesn't explicitly state when not to use it or mention alternatives beyond the sibling. However, the context is clear given only one sibling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityCmaintenanceCreate scheduling polls (like Doodle) from AI agents. Find the best time for meetings, dinners, and events. 5 tools: create_poll, get_poll, vote_on_poll, get_results, finalize_poll. No authentication required.5771MIT
- FlicenseNot gradedqualityDmaintenanceAutomates meeting logistics with tools for scheduling, availability checking, slot finding, timezone conversion, and recurring date generation. Eliminates the need for custom calendar logic by providing validated time operations and formatted invitations for applications and AI assistants.