UK Fitness Pro

Search personal trainers

search_trainers

Read-onlyIdempotent

Find personal trainers listed on UK Fitness Pro, a directory of personal trainers across the United Kingdom. Give a UK town, city, area or postcode as location (or online: true for trainers who coach remotely). Returns trainers within about 12 miles (20km), nearest first, with a link to each profile and to the full results page on the site. Use get_trainer_profile for a trainer's description, qualifications and pricing. If the resolved location is not the place the user meant (check area), call find_location and pass latitude/longitude instead. Verified means UK Fitness Pro has checked this trainer's identity documents. It does not confirm qualifications or insurance, which are as stated by the trainer. Most listed trainers are not verified. Listing is free, so absence of a badge says nothing negative.

Input Schema

Name	Required	Description
`sort`	No	distance (default; online searches are ordered verified first, then most recently updated) or price (lowest "from" price first; trainers without a price last).
`limit`	No	Maximum trainers to return. Default 10, maximum 25.
`gender`	No	Only trainers of this gender.
`online`	No	true for trainers offering online/remote coaching, regardless of location.
`latitude`	No	Use with longitude instead of location, e.g. a coordinate from find_location.
`location`	No	UK town, city, area or postcode, e.g. "Leeds", "Clapham", "M1 1AE", "SW19".
`longitude`	No	Use with latitude instead of location.
`speciality`	No	Only trainers listing a matching speciality, e.g. "weight loss", "rehabilitation", "boxing", "pre and postnatal". Matched loosely against the trainer's own speciality list.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond annotations (readOnly/openWorld/idempotent) by disclosing the return radius, nearest-first ordering, and the important caveat about what 'verified' does and does not mean, including that most trainers are unverified and free listing means absence of a badge is not negative. It also flags that geocoding can resolve to the wrong place and how to recover.

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?

Front-loaded with purpose and the core location/online usage decision, and the closing 'verified' explanation, while long, earns its place by preventing misreading of result badges. Slightly dense with caveats that could be trimmed.

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?

No output schema exists, yet the description covers return shape (links to profiles and the full results page) and result ordering. Combined with the 100% schema coverage and rich annotations, an agent has everything needed to call this correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds value by explaining the location/online alternatives and the latitude/longitude fallback as an error-recovery path. It does not add much on gender, speciality, limit, or sort beyond what the schema already states.

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?

Opens with a specific verb and resource ('Find personal trainers listed on UK Fitness Pro') and immediately scopes it to a UK directory with a stated ~12 mile radius. An agent can distinguish this from get_trainer_profile, find_location, and search_articles without opening any schema.

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?

Explicitly routes between alternatives: `location` vs `online: true`, get_trainer_profile for description/qualifications/pricing, and find_location when the resolved location is wrong. These are concrete when-to-use conditions tied to named siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All UK Fitness Pro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?