Skip to main content
Glama

Look something up

beleeg_look_up
Read-onlyIdempotent

Look something up in the person's Beleeg leagues. Read-only: nothing changes. Pick what, give only the params listed for it (league_id comes from beleeg_whoami), and relay the answer as written — times already carry their time zone. For what needs the person across all their leagues use beleeg_needs_me; for public pages by slug use beleeg_look_up_public.

what (params; ? = optional):

  • my_leagues: The leagues the person belongs to, their roles in each, and each league_id. [no params]

  • league_brief: A whole league in one call: teams with captains and roster sizes, standings, the schedule by week, recent results, tournaments. Best for broad questions. [league_id]

  • search_leagues: The public league directory, by name, sport or town — for leagues the person is not in. [query?]

  • standings: The standings table: rank, record, points, streak, last five, games back. [league_id, season_id?]

  • schedule: This season's matches, earliest first: date and time with zone, venue, sides, score; the match ids changes take. [league_id, from_date?, to_date?, team_id?, limit?]

  • divisions: The league's divisions and their ids. [league_id, season_id?]

  • seasons: Every season the league has run, newest first, with ids and dates. [league_id]

  • makeup_options: Days a rained-out or postponed match could be replayed on, and what each costs (league admins). [league_id, from_date?, match_ids?, horizon_days?]

  • teams: Every team in the league with its captain and roster user ids. [league_id, limit?]

  • members: Everyone in the league — name, email, roles, status — plus invites not yet accepted. [league_id, limit?]

  • my_team_assignment: The person's own team, line and role, as their captain set it. [league_id]

  • unpaid_members: Members who still owe the registration fee (league admins). [league_id]

  • tournaments: Every tournament the league has run or planned, with ids. [league_id, limit?, cursor?]

  • tournament_draws: The parallel draws (brackets) inside one tournament. [tournament_id, limit?]

  • tournament_court_schedule: One tournament's order of play: court, start time and referee per match. [tournament_id, limit?]

  • team_chat: Recent messages in a team's chat (people on the team only). [team_id, limit?, tournament_id?]

  • comms_status: Announcements already emailed to the league: subject, when, to whom, how many got it (league admins). [league_id, limit?]

  • articles: The league's published news posts and match recaps. [league_id, limit?, cursor?]

  • article_comments: Comments on one article or recap. [article_id, limit?]

  • tournament_photos: Photos uploaded for a tournament. [tournament_id, limit?]

  • tournament_highlights: Video highlights uploaded for a tournament. [tournament_id, limit?]

  • highlight_comments: Comments on one video highlight. [highlight_id, limit?]

  • referee_assignments: A tournament's referee assignments: match, court, time, referee. [tournament_id, limit?]

  • my_referee_alerts: How the calling referee is set up to hear about assignments. [no params]

  • my_availability: The person's own availability windows (an admin may name a user_id). [user_id?]

  • demo_league: Diagnostic snapshot of the demo league (Beleeg platform administrators only). [no params]

  • match_availability: Who can make a league match: each side's players grouped In, Out, Maybe and Hasn't answered. [league_id, match_id?]

  • match_checklist: The league's checklist for one match (the things every match needs — shot clock operator, snacks, nets put away) and who has answered what. [league_id, match_id?]

  • head_to_head: A team's record against one opponent in this league, across every season: won, lost, drawn, the total score, and the most recent results. [league_id, opponent, team?]

  • match_venue: Where a match is and what to know before going: the venue and its address with a map link, where to park, how to find the courts or field, what time to arrive by and what to wear, as the league set them. [league_id, match_id?]

  • calendar_link: The person's own calendar link: every match for every team they play on, which their phone or computer calendar keeps up to date by itself — a moved match moves in their calendar too. [no params]

  • match_proposals: Open requests to move a match that involve the person: ones waiting on them to accept, decline or approve, and ones their team is waiting on. [league_id]

  • standings_form: Each division's table this season with form: record, current streak (W3 = three wins in a row), last five results, and games behind the leader. [league_id]

  • find_team: Find a team by name across every league on Beleeg that lists itself publicly: its league, division, season, town, and a link to its public page (schedule, results, and a calendar anyone can subscribe to). [name]

  • open_disputes: Scores in dispute in this league: the match, the score one team put in, and the other team's reason. [league_id]

  • player_stats: Players' records this season, best first: matches won and lost, win percentage, and sets won and lost where the sport has sets. [league_id, player?]

  • team_dues_status: A team's dues (the kitty the captain collects): what they are for, how much, who has paid and who still owes. [league_id, team?]

  • scheduled_emails: League emails set to go out later: the subject, when each goes out (in the league's time), who it goes to, and any that could not be sent. [league_id]

  • referee_availability: The league's referees for one day: who is free, who already referees a match that day (and which), and who took the day off. [league_id, match_id?, date?]

  • events: Upcoming social events for this league and its organization: when, where, how many are going or maybe, spots left, the ticket price, and the person's own answer. [league_id, event?]

  • sponsors: The league's sponsors: applications waiting for an answer (who, what tier, what they offer), who is showing now, and how many were declined. [league_id]

  • store: The league store, read only: what is for sale and at what price, what is hidden, and the latest orders (who, what, total, status). [league_id]

  • waitlist: The league's waiting list in order (who, since when, who was already offered a spot) and how many spots are open now. [league_id]

  • ladder: The league's challenge ladder: every spot in order with each side's wins and losses, the challenges going on (who challenged whom, the answer deadline, the agreed time and place), any challenge waiting on the person's answer with its deadline, and who they… [league_id]

  • my_changes: Changes an assistant prepared or made for this person, and whether their emails actually went out. [limit?]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoThe day, as YYYY-MM-DD, when no match is named. Used with what: referee_availability.
nameNoThe team name, or part of it, e.g. "Hawks". At least two letters. Used with what: find_team.
teamNoA team, by name. Leave out for the person's own team. Used with what: head_to_head, team_dues_status.
whatYesWhat to look up. Every value is listed, with its params, in the tool description.
eventNoA word or two from one event's name, to see who is coming. Used with what: events.
limitNoMost rows to return. A list that is cut short says how many were left out. Used with what: schedule, teams, members, tournaments, tournament_draws, tournament_court_schedule, team_chat, comms_status, articles, article_comments, tournament_photos, tournament_highlights, highlight_comments, referee_assignments, my_changes.
queryNoWords to match against league name, organization, sport, or town. Omit to list everything public. Used with what: search_leagues.
cursorNoOpaque cursor from a previous page; leave out for the first page. Used with what: tournaments, articles.
playerNoOne player by name, or "me". Omit for the top ten. Used with what: player_stats.
team_idNoOnly matches involving this team. Used with what: schedule, team_chat.
to_dateNoOnly matches on or before this day, YYYY-MM-DD. Used with what: schedule.
user_idNoTarget user. Omit to return the calling user's own availability. Used with what: my_availability.
match_idNoOne match id (from what "schedule"). For the match-day lookups, leave out to mean the person's next match. Used with what: match_availability, match_checklist, match_venue, referee_availability.
opponentNoThe other team, by name, e.g. "Hawks". Used with what: head_to_head.
from_dateNoOnly matches on or after this day, YYYY-MM-DD. Omit for the whole season. Used with what: schedule, makeup_options.
league_idNoThe league id, from beleeg_whoami or what "my_leagues" (what "search_leagues" for a league the person is not in). Used with what: league_brief, standings, schedule, divisions, seasons, makeup_options, teams, members, my_team_assignment, unpaid_members, tournaments, comms_status, articles, match_availability, match_checklist, head_to_head, match_venue, match_proposals, standings_form, open_disputes, player_stats, team_dues_status, scheduled_emails, referee_availability, events, sponsors, store, waitlist, ladder.
match_idsNoSpecific matches instead of a whole day. Give this or from_date. Used with what: makeup_options.
season_idNoA past season, from what "seasons". Leave out for the season being played now. Used with what: standings, divisions.
article_idNoArticle whose comments to list. Used with what: article_comments.
highlight_idNoHighlight whose comments to list. Used with what: highlight_comments.
horizon_daysNoHow far ahead to look. Default 45 days. Used with what: makeup_options.
tournament_idNoA tournament id, from what "tournaments". Used with what: tournament_draws, tournament_court_schedule, team_chat, tournament_photos, tournament_highlights, referee_assignments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / league_id / description
      Previous value: -"The league id, from beleeg_whoami or what \"my_leagues\" (what \"search_leagues\" for a league the person is not in). Used with what: league_brief, standings, schedule, divisions, seasons, makeup_options, teams, members, my_team_assignment, unpaid_members, tournaments, comms_status, articles, match_availability, match_checklist, head_to_head, match_venue, match_proposals, standings_form, open_disputes, player_stats, team_dues_status, scheduled_emails, referee_availability, events, sponsors, store, waitlist."New value: +"The league id, from beleeg_whoami or what \"my_leagues\" (what \"search_leagues\" for a league the person is not in). Used with what: league_brief, standings, schedule, divisions, seasons, makeup_options, teams, members, my_team_assignment, unpaid_members, tournaments, comms_status, articles, match_availability, match_checklist, head_to_head, match_venue, match_proposals, standings_form, open_disputes, player_stats, team_dues_status, scheduled_emails, referee_availability, events, sponsors, store, waitlist, ladder."
    • changedInput schema / properties / what / enum
      Previous value: -[
      -  "my_leagues",
      -  "league_brief",
      -  "search_leagues",
      -  "standings",
      -  "schedule",
      -  "divisions",
      -  "seasons",
      -  "makeup_options",
      -  "teams",
      -  "members",
      -  "my_team_assignment",
      -  "unpaid_members",
      -  "tournaments",
      -  "tournament_draws",
      -  "tournament_court_schedule",
      -  "team_chat",
      -  "comms_status",
      -  "articles",
      -  "article_comments",
      -  "tournament_photos",
      -  "tournament_highlights",
      -  "highlight_comments",
      -  "referee_assignments",
      -  "my_referee_alerts",
      -  "my_availability",
      -  "demo_league",
      -  "match_availability",
      -  "match_checklist",
      -  "head_to_head",
      -  "match_venue",
      -  "calendar_link",
      -  "match_proposals",
      -  "standings_form",
      -  "find_team",
      -  "open_disputes",
      -  "player_stats",
      -  "team_dues_status",
      -  "scheduled_emails",
      -  "referee_availability",
      -  "events",
      -  "sponsors",
      -  "store",
      -  "waitlist",
      -  "my_changes"
      -]New value: +[
      +  "my_leagues",
      +  "league_brief",
      +  "search_leagues",
      +  "standings",
      +  "schedule",
      +  "divisions",
      +  "seasons",
      +  "makeup_options",
      +  "teams",
      +  "members",
      +  "my_team_assignment",
      +  "unpaid_members",
      +  "tournaments",
      +  "tournament_draws",
      +  "tournament_court_schedule",
      +  "team_chat",
      +  "comms_status",
      +  "articles",
      +  "article_comments",
      +  "tournament_photos",
      +  "tournament_highlights",
      +  "highlight_comments",
      +  "referee_assignments",
      +  "my_referee_alerts",
      +  "my_availability",
      +  "demo_league",
      +  "match_availability",
      +  "match_checklist",
      +  "head_to_head",
      +  "match_venue",
      +  "calendar_link",
      +  "match_proposals",
      +  "standings_form",
      +  "find_team",
      +  "open_disputes",
      +  "player_stats",
      +  "team_dues_status",
      +  "scheduled_emails",
      +  "referee_availability",
      +  "events",
      +  "sponsors",
      +  "store",
      +  "waitlist",
      +  "ladder",
      +  "my_changes"
      +]
  2. Added

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark this read-only, idempotent, and non-destructive, but the description adds important behavioral context: answers should be relayed as written, times already include their time zone, and several operations are restricted to league admins, team members, or platform admins. This goes well beyond the structured safety hints.

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?

The description is long, but the length is justified by 45 distinct operations and the absence of an output schema. It is front-loaded with global selection guidance, then uses a compact bulleted structure where each entry earns its place by naming the resource, params, and returned fields.

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?

Given the 22 parameters, the 45-value enum, no output schema, and the multiplexed design, the description is complete: it covers routing alternatives, permission scopes, parameter mapping, pagination hints via `limit`/`cursor`, and return content for every `what` value.

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

Parameters5/5

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

Schema description coverage is already 100%, yet the description still adds substantial value by grouping each `what` value with its valid parameters and optionality, and by describing what each operation returns. That operation-level mapping is more useful than the per-parameter schema alone for a 22-param multiplexer.

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 states a specific read-only lookup role in the person's Beleeg leagues and enumerates every supported resource via the `what` values. It explicitly distinguishes itself from siblings `beleeg_needs_me` and `beleeg_look_up_public`, so an agent can route correctly without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives explicit selection guidance: pick `what`, pass only the listed params, get `league_id` from `beleeg_whoami`, and use `beleeg_needs_me` or `beleeg_look_up_public` instead when those conditions apply. Each `what` entry also states admin-only or team-only restrictions where relevant.

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