Skip to main content
Glama

Get Coach

get_coach
Read-onlyIdempotent

Get the public profile of one SportPoint coach by slug (from search_coaches): sports, age groups, places and clubs where they train, bio, and up to ten upcoming sessions with price in EUR and spots left. Includes the profile url where the user can book.

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_coach"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe coach slug, as returned by search_coaches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and idempotency need no restating. The description adds some behavioral detail beyond them: the profile is public, includes only up to ten upcoming sessions (a result cap), prices are in EUR, and it returns a booking profile URL. It does not cover error behavior for an unknown slug.

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?

Two sentences, front-loaded with the verb, resource and key, followed by an efficient enumeration of returned fields. No filler or redundant restatement of the title.

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 appropriately enumerates return fields, the session cap, currency and booking URL, which an agent needs to interpret results. It stops short of covering failure modes such as an invalid or expired slug.

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% and the single parameter's description already says 'as returned by search_coaches', so the description's mention of the slug adds no meaning beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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 (Get) and resource (public profile of one SportPoint coach) plus the keying parameter (slug), and enumerates the returned fields so the agent knows exactly what it gets.

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?

'by slug (from search_coaches)' establishes the prerequisite workflow — obtain the slug from search_coaches first — which is clear usage context. It does not explicitly say when not to use it (e.g. use search_coaches for listing rather than repeated calls), but the routing to the prerequisite is unambiguous.

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