OriginGrid

Several discovery tools overlap heavily: discover, list, search, search_by_region, and resolve all return registry sources, and descriptions do not clearly differentiate when one should be preferred over another. There is also duplication between plan/execute_batch and search_session_create/execute, creating real risk of selecting the wrong tool.

All tools share the origingrid_ prefix and snake_case convention, and subgroups like search_session_* are well patterned. However, the action style is inconsistent: list, search, fetch, and get_source are verb-driven, while plan, feedback, stats, and pending_contributions are noun-style names, and contribute/discover are verbs with no object.

At 19 tools, the server is on the heavy side and feels inflated by near-duplicate discovery variants and two parallel plan-execution mechanisms. The domain is broad enough to justify many capabilities, but some of the search/discovery tools could plausibly be consolidated.

The core lifecycle is well covered: discover/search sources, fetch content, execute plans, submit feedback, and manage contributions through approve/reject. Minor gaps exist around source-card update/delete and session cancellation, but these do not create dead ends in the primary workflow.