Skip to main content
Glama

Find Sessions

find_sessions
Read-onlyIdempotent

Find upcoming training sessions on SportPoint (Bulgaria). Filter by sport, city, date or day, time of day, age group, level and maximum price in EUR. Sessions open for online booking come first. Each session has its date and times on the Europe/Sofia wall clock, price in EUR, spots left (null = no limit), whether online booking is open, and a url where the user books it. Twenty per page.

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

Input Schema

NameRequiredDescriptionDefault
dayNoA relative day on the Europe/Sofia clock; this_week runs to Sunday.
cityNoCity name in Bulgarian, e.g. "София".
dateNoOne calendar day, YYYY-MM-DD (Europe/Sofia). Wins over day.
pageNoResult page, starting at 1.
timeNoStart time band, Europe/Sofia wall clock.
levelNoLevel name as the club or coach wrote it, in Bulgarian (e.g. "Начинаещи").
sportNoSport name in Bulgarian (e.g. "Плуване") or its slug (e.g. "pluvane").
age_groupNoWho the session is for.
price_maxNoMaximum price per session in EUR.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses result ordering (online-bookable first), page size (twenty per page), the timezone basis of all dates and times (Europe/Sofia), the currency, and the exact meaning of each returned field including spots-left null semantics and the booking URL.

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?

Opens with what the tool returns, then filters, then ordering, then result shape and paging — each sentence carries distinct information with no repetition or filler.

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?

For a 9-parameter, zero-required search tool with no output schema, the description covers everything an agent needs: scope, available filters, sort order, page size, timezone, currency, and the per-session fields including the bookable URL.

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 every parameter is already documented in the schema, and the description merely restates the filter dimensions. It adds no syntax, precedence, or edge-case guidance beyond what the schema already says (e.g. that date wins over day), and it omits the paging parameter entirely. Baseline 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?

States a specific verb and resource ("Find upcoming training sessions") plus the domain (SportPoint, Bulgaria), which immediately separates it from sibling tools like get_club, get_coach, and search_clubs_and_places that return entity details rather than schedulable sessions.

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?

The filter list makes the intended query shapes clear (by sport, city, date/day, time band, age group, level, price cap), and the note that online-bookable sessions sort first signals when this tool is the right entry point for booking. It stops short of naming an alternative tool or stating any exclusions, so it earns a 4 rather than a 5.

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