Skip to main content
Glama

ELC Conference 2027: tickets, perks, partnerships

by io.github.marian-kamenistak
OverviewDiscussionsAdmin

plan-conference-journey

Read-onlyIdempotent

Help the user plan their ELC Conference 2027 day based on their role: priority themes, workshops, 1:1 mentoring and a game plan. The 2027 agenda is not published yet, so the plan uses the conference's topics and the 2026 format. IMPORTANT: Before calling this tool, always ask the user what their role is (CTO, VP of Engineering, Director of Engineering, Engineering Manager, Product Manager, Tech Lead, or Other).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoRequired. The user's role — used to prioritize tracks, sessions, and workshops One of: CTO, VP of Engineering, Director of Engineering, Engineering Manager, Product Manager, Tech Lead, Other.
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. Changed4 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 / role / description
      Previous value: -"The user's role — used to prioritize tracks, sessions, and workshops"New value: +"Required. The user's role — used to prioritize tracks, sessions, and workshops One of: CTO, VP of Engineering, Director of Engineering, Engineering Manager, Product Manager, Tech Lead, Other."
    • removedInput schema / properties / role / enum
      Removed value: -[
-  "CTO",
-  "VP of Engineering",
-  "Director of Engineering",
-  "Engineering Manager",
-  "Product Manager",
-  "Tech Lead",
-  "Other"
-]
    • removedInput schema / required
      Removed value: -[
-  "role",
-  "context"
-]
  2. 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: -[
-  "role"
-]New value: +[
+  "role",
+  "context"
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description still adds meaningful behavioral context: the 2027 agenda is not published and the plan is derived from topics plus the 2026 format, which tells the agent the output may be approximate.

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?

Purpose is front-loaded, followed by the data-freshness caveat and then the imperative instruction, so the most decision-relevant content leads. The IMPORTANT block is somewhat verbose with its full role enumeration, which the schema already lists.

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?

For a 2-param, read-only tool with no output schema and full annotation coverage, the description covers the purpose, the caveat about 2026-based planning, the deliverables, and the role precondition. Return structure is only implied via the listed deliverables, leaving a small gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds value by asserting that 'role' is effectively required and must be solicited before calling — the schema itself does not mark it required. It also frames 'context' as recorded intent that never changes the answer, reinforcing the schema note.

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+resource ('plan their ELC Conference 2027 day') and enumerates the actual deliverables (priority themes, workshops, 1:1 mentoring, a game plan). This is clearly distinct from purchasing/info siblings like buy-ticket, compare_packages, or get-conference-info, so an agent can route to it without opening a 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?

Provides clear usage context (personalized by role, and that it relies on 2026 format since the 2027 agenda is unpublished) plus an explicit precondition to collect the role first. It does not, however, name when to prefer this over alternatives like recommend_package or get-conference-info or state any exclusion.

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