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.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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'. |
TDQS
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). |
TDQS
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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
create_event2 fields changed- changed
Input schema / properties / earliest_hour / descriptionPrevious value: -"Earliest hour of day to consider, 0-23 (default 9)."New value: +"Earliest hour of day to consider, 0-23 (default 9). Ignored when mode='day'." - added
Input schema / properties / modeAdded value: +{ + "description": "'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.", + "enum": [ + "time", + "day" + ], + "type": "string" +}
2 tool updates
- First observed
create_event - First observed
get_event
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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 Connectors
Free no-signup group scheduling; share a link and rank times by who's free.
Find a time a group can meet: no-login availability poll that picks the best meeting slot.
21Group meeting scheduler — rank times everyone's free across Google & Outlook, book Meet/Teams.
Group scheduling: create a plan link, mark availability, get best times, lock the final time.
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.5921MIT
- AlicenseAqualityCmaintenanceEnables reading and filling when2meet scheduling polls over HTTP, including computing availability from weekly schedules or calendar busy times, previewing, and submitting availability, all without browser automation or OAuth.6MIT
- 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.-
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.3/5.0
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.