No user-submitted related servers found.
Scored across 2 tools
The two tools have clearly distinct roles: list_endpoints is pure discovery/metadata (path, params, verified, disabled flags) while get performs the actual API call against a path returned by discovery. There is no overlap in purpose, and the descriptions make the list-then-call workflow explicit.
Both names are lowercase snake_case imperative verbs, so the surface is consistent in style. However, 'get' is a bare generic verb that doesn't name its resource, unlike the well-formed 'list_endpoints', creating a minor asymmetry.
Two tools is deliberately thin but correct for a dynamic proxy pattern: one discovery tool plus one universal caller covers an entire API surface without per-endpoint tool bloat. It sits just under the typical 3-15 range but each tool clearly earns its place.
For a read-only personal-fitness API, the discovery-plus-GET design covers the whole surface, and range splitting, field filtering, truncation notes, and sensitive-endpoint gating are all handled. The gaps are the absence of any write/mutation operations and no dedicated auth or status check beyond the 'verified' flag.