A
license-
qualityD
maintenanceCreate visual whiteboards, diagrams, flowcharts, and project plans from AI conversations. 17 MCP tools for board management, element creation, and real-time collaboration.
1
MIT
Sessionplan
Server Details
Create and edit visual agendas for workshops, trainings, meetings, and events.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- tim-peters/sessionplan
- GitHub Stars
- 3
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, create_session_link and decode_session_link, have clearly distinct purposes—one generates new links, the other parses existing ones. There is no functional overlap or ambiguity between them.
Naming Consistency5/5
Both tool names follow the identical verb_noun pattern (create_/decode_ + session_link), making the naming scheme consistent and predictable.
Tool Count3/5
With only two tools, the server feels minimal. While the focus on session link creation and decoding is coherent, a typical server might also include listing or deleting sessions, making the count slightly thin for a general-purpose tool.
Completeness4/5
The two tools cover the primary lifecycle of creating and reading session links. Updates can be performed indirectly via decode + create, but there is no explicit update or delete tool, so full CRUD coverage is not achieved, though it is sufficient for the server's stated niche.
Available Tools
2 toolscreate_session_linkCreate SessionplanARead-onlyInspect
Use this when the user wants a new workshop agenda, training plan, meeting agenda, event schedule, facilitation plan, or other timed session as a directly openable Sessionplan link. This also covers German requests such as Agenda, Workshop-Ablauf, Trainingsplan, Meeting-Ablauf oder Event-Zeitplan. Build the complete session from the user's requirements and pass it as Sessionplan JSON. Never invent or manually construct a Sessionplan URL.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| session | Yes | Vollständiges Sessionplan-JSON gemäß der öffentlichen Sessionplan-Import-Spezifikation. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| link | Yes | Direkt öffnbarer Sessionplan-Link. |
Tool Definition Quality
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and destructiveHint. The description adds that the complete session must be built and passed as JSON and instructs never to invent or manually construct a URL, giving practical behavioral guidance without contradicting the annotations.
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 three sentences with no redundant information. It is direct, focused, and efficiently conveys the purpose and key requirement.
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?
The description adequately covers the use case and what to pass, but it does not mention any constraints like the maximum number of items (covered by schema) or any edge cases. For a creation tool with a single complex parameter, the description is sufficiently complete.
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?
The schema is very detailed and includes a description of the JSON specification. The description only says 'Build the complete session...' which adds minimal extra meaning about the parameter, and since schema coverage is 100%, the baseline is appropriate.
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 that the tool creates a directly openable Sessionplan link for new workshop agendas, training plans, and similar timed sessions, and it also covers German synonyms. This unambiguously distinguishes it from the sibling tool decode_session_link, which decodes links.
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?
It explicitly says 'Use this when the user wants a new...' which provides a clear trigger and also mentions German requests. However, it does not explicitly contrast with decode_session_link, though the scenario implies creation versus decoding.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
decode_session_linkOpen SessionplanARead-onlyInspect
Use this when the user provides an existing Sessionplan link and wants to view, summarize, review, validate, adapt, or modify the session. This also covers German requests such as zusammenfassen, prüfen, anpassen oder ändern. Decode the link first. If the user requests changes, modify the decoded session and then call create_session_link to generate a new link.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| link | Yes | Vollständige Sessionplan-URL, Hash oder v2-Snapshot-Code. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| session | Yes | Vollständiges Sessionplan-JSON gemäß der öffentlichen Sessionplan-Import-Spezifikation. |
Tool Definition Quality
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds context that the tool decodes the link first and that modifications are performed outside the tool, but it does not disclose failure scenarios or return structure. This is sufficient given the annotations and presence of an output schema.
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 concise, front-loaded with the core use case, and includes a practical workflow note. It avoids fluff and every sentence contributes actionable guidance, making it highly efficient.
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?
For a single-parameter read-only tool with full schema coverage and an output schema, the description covers all necessary aspects: when to use, language variants, and how to proceed with modifications. No critical information is missing.
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?
The schema description provides 100% coverage for the 'link' parameter, specifying it as a URL, hash, or v2 snapshot code. The description adds no further parameter-specific details, so the baseline of 3 is appropriate because the schema already carries the semantic load.
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 explicitly states the tool's purpose: to decode an existing Sessionplan link for viewing, summarizing, reviewing, validating, adapting, or modifying. It clearly distinguishes from the sibling create_session_link by outlining the workflow where this tool decodes first and create_session_link generates a new link afterward.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit usage conditions: 'Use this when the user provides an existing Sessionplan link' and covers German variants. It also gives a clear alternative/next step by instructing to call create_session_link after modifying, which effectively differentiates from the sibling tool.
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
- Alicense-qualityDmaintenanceEnables creating and iterating on animated SVG diagrams from text input, photos of sketches, and YAML specifications, with support for shapes, connections, SMIL animations, and file output.1MIT
- Alicense-qualityAmaintenanceA design studio where AI draws, charts and animates: agents create fully editable hand-drawn visuals, build charts from data, and their edits become stop-motion GIF and video animations. Free, offline, zero-dependency, MIT.2MIT
- Alicense-qualityBmaintenanceEnables AI assistants to create, edit, and export flowcharts through a local web-based editor with visual drag-and-drop, real-time sync, and 14 MCP tools for full node/edge CRUD.2Apache 2.0