No user-submitted related servers found.
Scored across 7 tools
Most tools target distinct actions: configure vs get_config are cleanly separated by direction, and parse_url is a focused utility. The only soft overlap is yapi_export_catalog with include_details=true, which can approximate the combined output of yapi_list_interfaces and yapi_get_interface, though the index-first default keeps them reasonably distinct.
Every tool uses the yapi_ prefix followed by a verb_noun form (get_config, parse_url, get_project, list_interfaces, get_interface, export_catalog), all in snake_case. No mixing of conventions.
Seven tools is well-scoped for a read-focused YApi client: two config tools, one URL helper, three resource reads, and one export. Each earns its place with no filler.
The read surface covers project metadata, interface listing, single-interface detail, and bulk catalog export, which fits the codegen/agent-understanding purpose. Gaps remain: there is no list_projects or interface search, so an agent starting from just a host must rely on parse_url or a known project_id, and no write/update operations exist.