# Reported issues for cal-scheduler Pod holds 7 of 7 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user. Back to [cal-scheduler](/mcp/cal-scheduler). ## Most discussed ### Release v1.1.3 ## Summary Cut release v1.1.3 — a PATCH bump for documentation improvements and a dev-dependency update. ## Problem Since v1.1.2, the following user-facing changes have landed on main but are not yet published: - Calendar tool descriptions now disclose their return shapes and key constraints (#106 / #107). - A Glama score badge and `glama.json` have been added to improve registry discoverability (#104 / #105). Additionally, the ruff dev dependency was bumped (#102). These changes are docs/reg [Read the thread](https://github.com/limey/cal-scheduler-mcp/issues/108) · 2026-08-16 · closed · outside contributor · 0 comments ### Improve create_calendar tool description to disclose contract and constraints ## Summary The `create_calendar` tool description is too terse for agents to use it confidently. Glama's TDQS breakdown flags it for missing behavioral transparency, parameter semantics, and usage guidance. We can fix this within PHILOSOPHY.md's "economical language" and CODING_STANDARDS.md's "docstring describes the contract" limits by expanding to a two-line description. ## Problem `create_calendar` currently says only: ```python \"\"\"Create a new calendar by display name.\"\"\" ``` This [Read the thread](https://github.com/limey/cal-scheduler-mcp/issues/106) · 2026-08-11 · closed · outside contributor · 0 comments ### Add Glama score badge and glama.json ## Summary Add the Glama score badge to `README.md` and add root `glama.json` for the claimed Glama listing. ## Problem The Glama listing is claimed, but the repo does not surface the Glama score badge and does not yet carry Glama's optional maintainer metadata file. Keep the change surgical: badge + `glama.json` only. ## Implementation notes - Add this score badge near the top of `README.md`, directly under the `# cal-scheduler` heading. Leave the leading `mcp-name` comment and agent pointer [Read the thread](https://github.com/limey/cal-scheduler-mcp/issues/104) · 2026-08-11 · closed · outside contributor · 0 comments ### Release v1.1.2 ## Summary Cut release v1.1.2 — a PATCH bump that updates the MCP SDK to 2.0 and refreshes dev/build dependencies. ## Problem The package currently pins `mcp>=1.28.0,<2`, but MCP SDK 2.0 is now available and the server code has been adapted to the new `MCPServer` class. Shipping a release makes this compatibility available to users via PyPI and the MCP Registry. ## Rationale for PATCH (not MINOR) The public tool surface is unchanged; only internal compatibility and dependency constraints were [Read the thread](https://github.com/limey/cal-scheduler-mcp/issues/100) · 2026-08-10 · closed · outside contributor · 0 comments ### Release v1.1.1 ## Summary Cut release v1.1.1 — a PATCH bump aggregating documentation improvements, dependency updates, and CI publishing enhancements since v1.1.0. ## Problem Since v1.1.0 the following user-facing changes have landed on `main` but are not yet available on PyPI: - README now documents the PyPI shim wiring form alongside the existing clone-based example. - AGENTS.md notes the need to reload or restart the MCP host after wiring config changes, and no longer hard-codes the tool count so docs st [Read the thread](https://github.com/limey/cal-scheduler-mcp/issues/94) · 2026-07-23 · closed · outside contributor · 0 comments ### docs(readme): add PyPI-only cal-scheduler shim wiring example ## Summary Add a pure-PyPI wiring example to the README's MCP configuration section so an agent that installed `cal-scheduler-mcp` from PyPI can copy-paste a working `mcpServers` block without improvising the shim path. ## Problem The README currently shows only the `uv run --directory /abs/path/to/clone` form. That form is correct for development or a clone-based install, but an agent that followed the documented `uv tool install cal-scheduler-mcp` path has no matching example. It must guess [Read the thread](https://github.com/limey/cal-scheduler-mcp/issues/90) · 2026-07-22 · closed · outside contributor · 0 comments ### Automate MCP Registry publishing in release workflow ## Summary Add an automated MCP Registry publish step to the existing `publish.yml` workflow, so every PyPI release tag also updates the listing on `registry.modelcontextprotocol.io` without manual `mcp-publisher` invocation. ## Problem The MCP Registry listing at `io.github.limey/cal-scheduler-mcp` currently requires manual intervention on every release: install `mcp-publisher`, `login github`, `publish`. This is error-prone (v1.1.0 shipped to PyPI but was missed for the registry until now) [Read the thread](https://github.com/limey/cal-scheduler-mcp/issues/86) · 2026-07-16 · closed · outside contributor · 0 comments ## Most recent The remaining reports are on [the project's issue tracker](https://github.com/limey/cal-scheduler-mcp/issues).