Skip to main content
Glama

Search Coaches

search_coaches
Read-onlyIdempotent

Search the sports coaches listed on SportPoint (Bulgaria). Filter by sport, city, age group or free text (coach name or sport). Returns ten coaches per page, each with a public profile url. Sport and city values are in Bulgarian; call list_sports_and_cities for the valid values.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name in Bulgarian, e.g. "София".
pageNoResult page, starting at 1.
sportNoSport name in Bulgarian (e.g. "Плуване") or its slug (e.g. "pluvane").
searchNoFree text matched against coach names and sport names.
age_groupNoWho the coach trains.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world behavior, and the description adds genuinely new facts: page size of ten, that each result carries a public profile URL, and that sport/city inputs must be Bulgarian. It omits ordering/ranking of results and any total-count or truncation behavior.

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?

Four short sentences, front-loaded with the resource and scope, then filters, then return shape, then the input-language constraint and helper tool. Nothing is redundant and the actionable constraint (Bulgarian values) is not buried.

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 usefully discloses the return shape (ten per page, profile URL) and the language prerequisite. Minor gaps remain around pagination limits and result ordering, but an agent has enough to call it correctly.

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 all five parameters are already documented, and the description largely restates them (sport, city, age group, free text). It adds only marginal semantics, such as clarifying that free text matches coach names and sport names, so baseline 3 is correct.

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 ("Search the sports coaches") plus the domain ("SportPoint (Bulgaria)") and the exact filter dimensions, so it is immediately distinguishable from the sibling search_clubs_and_places or find_sessions by the resource noun alone.

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 an explicit routing instruction to call list_sports_and_cities for valid sport/city values, and the free-text clause implicitly routes name lookups here. It does not state when to prefer this over get_coach for a known coach, so it stops short of full when/when-not guidance.

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