LONG Events

get_event_weeks

Read-onlyIdempotent

List upcoming conference weeks, festivals, and multi-day event series (like ETH Denver, Devconnect, Token2049). Use this to help users plan trips around major conferences.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_event_weeks"
  }
}

Input Schema

Name	Required	Description
`tag`	No	Filter by tag (e.g., 'crypto', 'music', 'tech')
`city`	No	Filter by city name
`limit`	No	Maximum number of event weeks to return
`country`	No	Filter by country name
`include_past`	No	Include past event weeks (default false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 8, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful context that results are 'upcoming' and include multi-day event series, but does not disclose additional behaviors like sorting, pagination, or whether summaries vs. full details are returned.

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?

Two compact sentences with no filler: the first front-loads the action and resource, the second gives the use case. The examples are high-value and every sentence earns its place.

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 simple read-only list tool with five optional parameters fully documented in the schema, the description is largely complete: it names the resource, scope, and use case. The only noticeable gap is not pointing to search_event_weeks or get_event_week_details when a more targeted query or deeper detail is needed, but this is minor given the low complexity.

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%, so the schema fully documents all five parameters. The description adds no parameter-specific meaning beyond what the schema already provides, so the baseline score 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 uses a specific verb ('List') and names the exact resource: upcoming conference weeks, festivals, and multi-day event series, with concrete examples (ETH Denver, Devconnect, Token2049). This clearly differentiates it from search-oriented siblings like search_event_weeks or detail tools like get_event_week_details.

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 states the intended use case: helping users plan trips around major conferences. However, it does not name alternatives or state when NOT to use this tool, such as when the user needs a free-text search for a specific event week name.

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

All LONG Events tools Inspect

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

Need Help?