Skip to main content
Glama

List events

list_events
Read-onlyIdempotent

Upcoming arrangements and courses, GLØDI's own and the clinics', with sessions, seats left, price from and registration state. event_id reads one event with its program, prerequisites and price tiers.

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
pageNo
typeNoArrangements or courses.
localeNoAnswer language: nb (Norwegian) or en.nb
event_idNoOne event with its program.
clinic_idNoThe clinic_id find_clinics returns. Never build it from a name. A clinic site needs none.
from_dateNoOnly sessions from this day (YYYY-MM-DD); default today.
page_sizeNo

Output Schema

NameRequiredDescriptionDefault
nextYes
countYes
resultsYes
previousYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedOutput schema / properties / results / items / properties / arrangement_id
      Added value: +{
      +  "description": "register_for_event takes it to register the whole arrangement.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / pricing_tiers / items / properties / pricing_tier_id
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / results / items / properties / pricing_tiers / items / required
      Previous value: -[
      -  "name",
      -  "price_nok"
      -]New value: +[
      +  "pricing_tier_id",
      +  "name",
      +  "price_nok"
      +]
    • addedOutput schema / properties / results / items / properties / sessions / items / properties / session_id
      Added value: +{
      +  "description": "register_for_event takes it to register this session.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / results / items / properties / sessions / items / required
      Previous value: -[
      -  "date",
      -  "start",
      -  "end",
      -  "seats_left"
      -]New value: +[
      +  "session_id",
      +  "date",
      +  "start",
      +  "end",
      +  "seats_left"
      +]
    • changedOutput schema / properties / results / items / required
      Previous value: -[
      -  "event_id",
      -  "title",
      -  "type",
      -  "host",
      -  "venue",
      -  "sessions",
      -  "is_full",
      -  "price_from_nok",
      -  "registration_open",
      -  "url",
      -  "description",
      -  "program",
      -  "prerequisites",
      -  "pricing_tiers",
      -  "waitlist"
      -]New value: +[
      +  "event_id",
      +  "arrangement_id",
      +  "title",
      +  "type",
      +  "host",
      +  "venue",
      +  "sessions",
      +  "is_full",
      +  "price_from_nok",
      +  "registration_open",
      +  "url",
      +  "description",
      +  "program",
      +  "prerequisites",
      +  "pricing_tiers",
      +  "waitlist"
      +]
  2. Changed3 schema fields changed
    • addedOutput schema / properties / results / items / properties / program
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "day": {
      +        "description": "The day of the program, from 1.",
      +        "type": "integer"
      +      },
      +      "description": {
      +        "type": "string"
      +      },
      +      "title": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "day",
      +      "title",
      +      "description"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / properties / results / items / properties / program_modules
      Removed value: -{
      -  "items": {
      -    "additionalProperties": false,
      -    "properties": {
      -      "description": {
      -        "type": "string"
      -      },
      -      "title": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "title",
      -      "description"
      -    ],
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
    • changedOutput schema / properties / results / items / required
      Previous value: -[
      -  "event_id",
      -  "title",
      -  "type",
      -  "host",
      -  "venue",
      -  "sessions",
      -  "is_full",
      -  "price_from_nok",
      -  "registration_open",
      -  "url",
      -  "description",
      -  "program_modules",
      -  "prerequisites",
      -  "pricing_tiers",
      -  "waitlist"
      -]New value: +[
      +  "event_id",
      +  "title",
      +  "type",
      +  "host",
      +  "venue",
      +  "sessions",
      +  "is_full",
      +  "price_from_nok",
      +  "registration_open",
      +  "url",
      +  "description",
      +  "program",
      +  "prerequisites",
      +  "pricing_tiers",
      +  "waitlist"
      +]
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral content by disclosing what the listing carries (sessions, seats left, price-from, registration state) and that the event_id mode returns prerequisites and tiers. It says nothing about pagination behavior, default result scope, or ordering, which would raise it further.

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?

Two dense sentences, no filler, with the primary listing purpose front-loaded before the event_id detail mode. The telegraphic fragment style ('price from and registration state') is compact but reads slightly clipped rather than broken.

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?

An output schema exists, so return values need no prose, and the safety profile is fully annotated. For a 7-parameter read-only listing tool the description covers scope and the two operating modes adequately. It could still state default behaviour (all upcoming, today onward) and pagination limits to be fully self-sufficient.

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 coverage is 71% with both enums documented in-schema, so the baseline is 3. The description genuinely adds meaning for event_id, clarifying that it is a detail mode returning program, prerequisites and price tiers, and it implies scope for clinic_id via 'the clinics''. It does not explain page/page_size interaction or the all-upcoming default when no dates are supplied.

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 concrete resource and scope: upcoming arrangements and courses, both GLØDI's own and clinics', with sessions, seats left, price-from and registration state. That is a specific data profile an agent can match against a request. It stops short of naming a sibling (e.g. list_offers) to delineate the boundary.

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?

The only explicit selection rule is the event_id clause: passing an id switches to single-event detail with program, prerequisites and price tiers. There is no statement of when to prefer this over list_offers, register_for_event, or browse_site, and no exclusions. Usage is implied by the content described rather than instructed.

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