Skip to main content
Glama

ELC Conference 2027: tickets, perks, partnerships

by io.github.marian-kamenistak
OverviewDiscussionsAdmin

get-available-tickets

Read-onlyIdempotent

Ticket status and prices for ELC Conference 2027 in Prague, checked live against the ticket shop. While 2027 tickets are not on sale it says so, links the notify list and shows 2026 prices clearly labelled as 2026. Never quote a 2027 price this tool did not return.

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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."
    • removedInput schema / required
      Removed value: -[
-  "context"
-]
  2. Changed2 schema fields changed
    • 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"
+}
    • addedInput schema / required
      Added value: +[
+  "context"
+]
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover readOnly/openWorld/idempotent/non-destructive, yet the description adds real behavioral context: it checks live against the shop, reports the not-on-sale state honestly, links the notify list, and labels 2026 prices as 2026. The closing guardrail against quoting unreturned 2027 prices further constrains agent behavior beyond anything in structured fields.

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, front-loaded with purpose, followed by behavioral detail and a guardrail. Efficient and well ordered, though the 2026 labelling is stated twice ('clearly labelled as 2026'), a small redundancy.

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?

With no output schema and a single optional parameter, the description carries the return-value burden and does so: it tells the agent what comes back (status, prices, notify-list link) and how to interpret the off-sale state. Nothing an agent needs to call or report on this tool correctly 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?

There is one optional parameter with 100% schema description coverage, so the schema fully documents 'context'. The description adds nothing about it, which is acceptable but yields the baseline 3 rather than a higher mark.

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?

States a specific verb (get) and resource (available tickets) scoped to ELC Conference 2027 in Prague, and the phrase 'checked live against the ticket shop' pins down that it is a live status/price read rather than a purchase or listing tool. An agent can distinguish it from buy-ticket and list_packages without opening any schema.

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?

Clearly frames the scenario in which the tool is the right call (any time ticket status or prices are needed) and describes the fallback path when 2027 tickets are not yet on sale. It does not explicitly name alternatives like buy-ticket or list_packages, so it stops short of full when/when-not routing.

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