mako-neighborhoods

To get complete context for a database table during codebase investigation, you can retrieve an entity-centered context bundle that includes schema, RLS, readers, writers, routes, and RPCs. This provides one composed context instead of requiring multiple primitive calls.

Tracing callers and handlers for an RPC endpoint is best done by pulling a route or RPC neighborhood. This retrieves implementation evidence, touched tables, imports, and downstream database touchpoints in a single bundle for fast analysis.

Yes, you can inspect RLS policy context and database touchpoints for a specific route. The route context feature gathers handlers, imports, RPCs, and nearby policy context to support endpoint investigations without manual query chaining.

Yes, you need MCP neighborhood tools to retrieve entity-centered schema context. The feature relies on these tools to compose the full bundle of schema, readers, writers, and touchpoint analysis for the specified table, route, or RPC.

To log structured agent feedback on a problematic context bundle result, you use the optional feedback logging workflow. This requires a prior tool run to exist, allowing you to record whether the retrieved bundle results were useful or problematic.

You should avoid using a composed neighborhood bundle when you only need a single isolated piece of schema information. The bundle is designed for broad entity-centered investigations where gathering RLS, readers, writers, and touchpoints together is better than primitive calls.