Skip to main content
Glama

ELC Conference 2027: tickets, perks, partnerships

by io.github.marian-kamenistak
OverviewDiscussionsAdmin

buy-ticket

Read-onlyIdempotent

Buy ELC Conference 2027 tickets: returns the live purchase link when tickets are on sale, otherwise says plainly that they are not on sale yet and gives the notify list, with a 2026 reference cost for groups (team pack sold as 4+1 free in 2026). IMPORTANT: before calling, ask the user how many people the tickets are for and pass that as 'quantity'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextNoOptional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.
quantityNoRequired. Number of people attending. 2027 tickets are not on sale yet; with the head count the answer gives the notify list and a 2026 reference cost for the group.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / quantity / description
      Previous value: -"Required. Number of people attending"New value: +"Required. Number of people attending. 2027 tickets are not on sale yet; with the head count the answer gives the notify list and a 2026 reference cost for the group."
  2. Changed6 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Explain 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.\""New value: +"Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer."
    • changedInput schema / properties / quantity / description
      Previous value: -"Number of people attending"New value: +"Required. Number of people attending"
    • removedInput schema / properties / quantity / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / quantity / minimum
      Removed value: -1
    • changedInput schema / properties / quantity / type
      Previous value: -"integer"New value: +[
+  "number",
+  "string"
+]
    • removedInput schema / required
      Removed value: -[
-  "quantity",
-  "context"
-]
  3. Changed1 schema field changed
    • addedInput schema / properties / quantity / maximum
      Added value: +9007199254740991
  4. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Explain 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.\"",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "quantity"
-]New value: +[
+  "quantity",
+  "context"
+]
  5. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuine behavioral context beyond that: the two possible outcome states, the notify list, and the 2026 group reference cost (4+1 free team pack). It stops short of mentioning availability windows, rate limits, or whether the link expires.

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?

Three sentences, no padding, with the outcome behavior front-loaded and the pre-call requirement flagged with 'IMPORTANT'. Mildly long but every clause carries information.

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?

There is no output schema, so the description must carry the return-value burden — and it does, describing both branches of the response. Combined with rich annotations, an agent has enough to call it correctly, though nothing is said about what to do with the returned link.

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% with only 2 params, so the schema already documents both. The description reinforces the quantity requirement and its effect, but adds little syntax or format detail beyond what the schema states; the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource (buy ELC Conference 2027 tickets) and, crucially, what the tool actually returns: a live purchase link when tickets are on sale, or a plain 'not on sale yet' message with the notify list otherwise. It does not name any sibling (e.g. get-available-tickets, get-package) to explicitly differentiate itself, so it falls just short of a 5.

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 gives a clear pre-call prerequisite ('before calling, ask the user how many people the tickets are for and pass that as quantity'), which is real actionable guidance. It does not, however, say when to prefer this over the sibling ticket/package tools or any when-not-to-use condition.

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

All ELC Conference 2027: tickets, perks, partnerships toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources