Skip to main content
Glama

Get Club

get_club
Read-onlyIdempotent

Get one SportPoint club by slug (from search_clubs_and_places): description, places, coaches, and one Monday-to-Sunday week of its sessions with price in EUR and spots left. Pass week as any date (YYYY-MM-DD) in the wanted week; the default is the current week.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_club"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe club slug, as returned by search_clubs_and_places.
weekNoAny date (YYYY-MM-DD) in the week to show. Defaults to the current week.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered; the description adds real context beyond them by specifying the returned payload shape, the default week (current week), the currency (EUR) and the presence of remaining-spot counts. It stops short of stating pagination or whether session lists can be truncated, which is the only notable behavioral gap.

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 sentences, both front-loaded: identity and payload first, date semantics second. Dense but every clause carries information, though the parenthetical slug provenance and the week sentence partially duplicate the schema-description text, so it is not maximally tight.

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?

With no output schema, the description compensates by enumerating returned fields, and it covers the non-obvious temporal parameter behavior. For a two-parameter read tool this is close to complete; only edge cases around the week window and response size are unaddressed.

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 100%, so both parameters are already documented, and the description largely restates them: the slug provenance and the 'any date in the wanted week' semantics with the current-week default. It adds no format nuances (timezone handling, week boundary edge cases) beyond what the schema fields already say, so the baseline of 3 applies.

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 ('Get one SportPoint club by slug') and then enumerates exactly what comes back: description, places, coaches, and one Monday-to-Sunday week of sessions with price in EUR and spots left. That return-content enumeration also separates it implicitly from get_place and get_coach, which return only the nested entities this tool bundles.

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?

Gives a clear entry path: the slug comes 'from search_clubs_and_places', so an agent knows how to obtain the required input. It does not say when to prefer get_place / get_coach / find_sessions over this tool, so there are no explicit exclusions, only a positive usage signal.

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