Skip to main content
Glama

Server Details

Group scheduling: create a plan link, mark availability, get best times, lock the final time.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
80.0% over 64 days
Last Tested
Transport
Streamable HTTP
URL

TDQS

A4.4/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct aspect of the planning lifecycle—creation, retrieval, availability marking, time locking, place setting, best-times calculation, and successor planning—with no overlapping purposes.

Naming Consistency5/5

All tools follow the consistent pattern 'whenna_<verb>_<noun>' (e.g., whenna_create_plan, whenna_lock_time), with lowercase snake_case throughout, making the set predictable and easy to navigate.

Tool Count5/5

With 7 tools covering the essential operations for a meeting scheduling service, the count is well-scoped and each tool earns its place without redundancy or bloat.

Completeness4/5

The toolset covers the full workflow: create, retrieve, mark availability, lock time, set place, compute best times, and chain to the next plan. Minor gaps exist (e.g., no explicit delete or plan-edit tool), but the core lifecycle is fully supported.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updates
    • Changedwhenna_mark_availability5 fields changed
      • changedInput schema / properties / free / description
        Previous value: -"Free ranges. Empty array clears this participant's availability."New value: +"Free ranges. Empty array = explicit \"can't make any\"."
      • addedInput schema / properties / free / items / properties / day / description
        Added value: +"YYYY-MM-DD date, or a weekday name (e.g. \"Tuesday\") for weekly plans"
      • removedInput schema / properties / free / items / properties / day / pattern
        Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
      • addedInput schema / properties / withdraw
        Added value: +{
        +  "description": "Remove this participant's answer entirely (ignores free).",
        +  "type": "boolean"
        +}
      • changedInput schema / required
        Previous value: -[
        -  "id",
        -  "name",
        -  "free"
        -]New value: +[
        +  "id",
        +  "name"
        +]
    • Addedwhenna_plan_next
    • Addedwhenna_set_place
  2. 1 tool update
    • Changedwhenna_lock_time4 fields changed
      • addedInput schema / properties / day / description
        Added value: +"YYYY-MM-DD date, or a weekday name for weekly plans (matching the plan's days)"
      • removedInput schema / properties / day / pattern
        Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
      • addedInput schema / properties / use_best
        Added value: +{
        +  "description": "Lock the current #1 best time (most participants free); day/start not needed.",
        +  "type": "boolean"
        +}
      • changedInput schema / required
        Previous value: -[
        -  "id",
        -  "creator_key",
        -  "day",
        -  "start"
        -]New value: +[
        +  "id",
        +  "creator_key"
        +]
  3. 1 tool update
    • Changedwhenna_create_plan1 field changed
      • addedInput schema / properties / language
        Added value: +{
        +  "description": "Optional 2-letter language for emails to notify_email (en es pt fr de it nl ru tr id hi ja ko zh ar). Default en.",
        +  "type": "string"
        +}
  4. 1 tool update
    • Changedwhenna_create_plan3 fields changed
      • changedInput schema / properties / days / description
        Previous value: -"Candidate days: YYYY-MM-DD dates, OR weekday names (Mon…Sun / Monday…Sunday) for a weekly recurring plan. Do not mix the two."New value: +"Candidate days: YYYY-MM-DD dates; OR weekday names (Mon…Sun) for weekly; OR [\"daily\"]; OR for monthly a single rule like [\"15\"] (day of month) or [\"2nd Wednesday\"] / [\"last Friday\"]. Do not mix forms."
      • addedInput schema / properties / every_weeks
        Added value: +{
        +  "default": 1,
        +  "description": "Repeat interval for recurring plans (with frequency: 2+weekly = every other week, 2+monthly = every other month, 3+daily = every 3 days)",
        +  "maximum": 12,
        +  "minimum": 1,
        +  "type": "integer"
        +}
      • addedInput schema / properties / frequency
        Added value: +{
        +  "description": "How a recurring plan repeats. monthly requires days to be one rule: a day-of-month (\"15\") or an nth weekday (\"2nd Wednesday\", \"last Friday\"). Default weekly.",
        +  "enum": [
        +    "daily",
        +    "weekly",
        +    "monthly"
        +  ],
        +  "type": "string"
        +}
  5. 1 tool update
    • Changedwhenna_create_plan4 fields changed
      • changedInput schema / properties / days / description
        Previous value: -"Candidate days, YYYY-MM-DD"New value: +"Candidate days: YYYY-MM-DD dates, OR weekday names (Mon…Sun / Monday…Sunday) for a weekly recurring plan. Do not mix the two."
      • removedInput schema / properties / days / items / pattern
        Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
      • addedInput schema / properties / location
        Added value: +{
        +  "description": "Optional place (\"Nonna's, 5th Ave\") — shown on the plan and embedded in everyone's calendar event",
        +  "maxLength": 120,
        +  "type": "string"
        +}
      • addedInput schema / properties / notify_email
        Added value: +{
        +  "description": "Optional creator email: gets an alert on the first answer, digests after, a \"everyone's free\" moment, and the lock confirmation. Every email has one-click unsubscribe.",
        +  "type": "string"
        +}
  6. 5 tool updates
    • First observedwhenna_best_times
    • First observedwhenna_create_plan
    • First observedwhenna_get_plan
    • First observedwhenna_lock_time
    • First observedwhenna_mark_availability

Related MCP Connectors

Related MCP Servers

  • F
    license
    Not graded
    quality
    D
    maintenance
    Enables scheduling polls for group chats to find common available times, with tools to create polls, get results, add candidate slots, and finalize appointments.
    -
  • A
    license
    A
    quality
    C
    maintenance
    Create 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.
    5
    44 npm
    1
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources