Skip to main content
Glama

List upcoming dates

list_events
Read-onlyIdempotent

Upcoming training dates sorted by date: course, start and end (Belgrade time), format, location or online, seats left, price, language and the registration url. courseSlug narrows to one course.

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": "list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: en, de or sr. Default en.en
takeNoHow many to return, at most 20
courseSlugNoThe slug as another tool returned it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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, closed-world), so the description's job is to add content-level behavior — and it does, disclosing sort order, the Belgrade timezone for dates, and the full set of returned fields in the absence of an output schema. It does not mention the default page size or how to get more than one page, which keeps it below 5.

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?

The returned-field inventory is front-loaded and the scoping note comes last, with no filler sentences. The long comma-separated field list is dense but each item carries information an agent would otherwise have to guess.

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 three-parameter, no-output-schema read tool, the description supplies the most important missing piece: what a result row looks like, including timezone and currency-adjacent fields like price. Only pagination behavior and default result count are left unaddressed, which is minor given the schema defaults.

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 already documents lang, take (default 10, max 20) and courseSlug. The description adds only that courseSlug narrows to a single course, and says nothing about lang or count that the schema does not already say. 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 names a specific resource ('upcoming training dates') and enumerates exactly what each entry contains (course, start/end in Belgrade time, format, location/online, seats left, price, language, registration url). That is enough for an agent to tell it apart from siblings like get_course or search_courses. It lacks an explicit verb and does not name a competing alternative, so it falls 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the tool returns upcoming dates, and 'courseSlug narrows to one course' is a scoping hint rather than a when-to-use rule. There is no statement about when to prefer get_course or search_courses, or that only future dates are covered. Adequate but with clear gaps.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources