myco:api-endpoint-serializer-authoring

Classify it as a resource or action endpoint, then use Cursor and paginate() from services/pagination.py to decode the cursor and return a page plus next cursor. Default limit is 50 with a maximum of 200, and the cursor is exposed as an opaque query-string parameter.

Use the @register_serializer decorator with the tools={...} dict form mapping each tool name to a RenderKind, then implement a static serialize method. The tool_name=/kind= keyword form does not exist; single-tool registrations can pass a list instead.

Resource endpoints return HTTP 409 when the required product is absent because the resource is implied to exist. Action endpoints always return HTTP 200 with a capability_not_available envelope, never 404 or 409.

The test requires every read tool to have a registered GET route whose name follows the default convention. If your route function name differs, add an entry to TOOL_ROUTE_OVERRIDES in the test file, but note this mapping is test-only and does not register the route itself.

No. apps/api may only import from unifi-core; importing unifi-mcp-shared is a build-time error because it couples the REST server to MCP protocol concerns. Serializers and render hints likewise stay in apps/api and never leak into managers or MCP tools.