feat(drops): align list tool filters

What changed

The drops list tool for Model Context Protocol now accepts project_id and query arguments alongside the existing domain, source type, and pagination inputs. Those values are passed through to the same drops listing context used by the dashboard.

The dedicated tool tests now cover project filtering, title and body search, and pagination metadata.

Why

The dashboard already lets people filter drops by project, domain, source type, and free-text search. Clients using Model Context Protocol could page through drops, but could not express the full dashboard query.

Approach

The tool schema and call path stay backward-compatible. Existing domain_id, source_type, page, and page_size arguments keep their behavior, while project_id maps to the underlying project filter and blank search strings are ignored before calling the drops context.

Impact

Clients can ask for the same filtered drops they see in the dashboard without over-fetching and filtering locally. Existing callers keep their current behavior.

Validation

• mix format lib/hive/mcp/components/tools/list_drops.ex test/hive/mcp/components/tools/list_drops_test.exs
• mix test test/hive/mcp/components/tools/list_drops_test.exs test/hive/mcp/server_test.exs

No GitHub comments yet.