Skip to main content
Glama

elc-conference-mcp-tickets

by io.github.marian-kamenistak

add-to-calendar

Read-onlyIdempotent

Add ELC Conference 2026 to the user's calendar. Returns a one-click Google Calendar link and a downloadable .ics file link that works with Apple Calendar, Outlook, and any other calendar app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextYesExplain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by explaining what the tool actually returns: a one-click Google Calendar link and a downloadable .ics file, and that the .ics works across calendar apps. It could be slightly clearer that the tool itself does not write to the calendar directly, but the link-based output is disclosed.

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 a single concise sentence that front-loads the action and immediately specifies the output formats and compatibility. Every clause carries useful information with no filler.

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?

This is a simple link-generation tool with one self-documented parameter and rich annotations. The description fully explains the output and compatibility, so an agent has everything needed to select and invoke the tool correctly.

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?

Schema description coverage is 100%, and the lone parameter `context` already has very detailed instructions about length, perspective, and content. The tool description does not need to repeat that information, so the baseline of 3 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 names a specific action and resource: adding ELC Conference 2026 to the user's calendar. It also clearly distinguishes the tool from siblings by mentioning the exact output: Google Calendar and .ics file links. This is far more specific than the generic title and leaves no ambiguity about what the tool does.

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 makes the intended use obvious: call this tool when the user wants ELC Conference 2026 added to their calendar or wants calendar integration links. It does not explicitly exclude alternatives, but among the siblings (buy-ticket, get-conference-info, etc.), this is the only calendar-add tool, so context alone is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All elc-conference-mcp-tickets toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Each domain tool maps cleanly to a distinct action—informational, purchasing, planning, calendar—and descriptions clarify boundaries. The only mild ambiguity is between the meta tools get-started and get_more_tools, which both touch capability discovery.

Naming Consistency4/5

Seven of eight tools follow a clear verb-noun kebab-case pattern, making the set predictable. get_more_tools breaks the pattern with an underscore and a less consistent phrase, preventing a perfect score.

Tool Count5/5

At eight tools, the set is well within the ideal range and each tool serves a clear purpose for conference ticket and concierge workflows. The two meta tools are justified for routing and extensibility, so nothing feels padded or missing.

Completeness4/5

The surface covers the core journey: conference info, availability, purchase, calendar add, role-based planning, and recommendation. Missing explicit cancellation/refund or order-lookup operations, but those are workable gaps, not dead ends.

Resources