feat: add a tool catalog and local MCP server

Define tools that answer questions from the app's data once, independent
of the surface that exposes them. A tool declares its arguments and the
services it reads; applications compose tools with their own services and
optional call interceptors. Queries reuse the layers' portable source
factories, so they run wherever an application routes /api requests.

The first queries are get_earthquakes, get_active_fires and
get_recent_launches, with a shared area argument (place name, bounding
box, or point and radius) and capped lists.

gods-eye-view/tools/mcp adapts a catalog to the Model Context Protocol
with a small JSON-RPC handler and a stateless HTTP transport, adding no
dependencies. npm run mcp serves Core's tools over stdio to local clients
such as Claude Code, reading from a running app. Both exports are
portable and checked by check:boundaries; the app does not import them.

src/tools/index.js

@@ -0,0 +1,24 @@
+/**
+ * Tools that answer questions from God's Eye View data, independent of the
+ * surface that exposes them. See docs/TOOLS.md.
+ */
+
+import { getActiveFires, getEarthquakes } from './queries/hazards.js';
+import { getRecentLaunches } from './queries/space.js';
+
+export {
+  defineTool,
+  composeCatalog,
+  ToolError,
+  TOOL_ERROR_CODES,
+} from './catalog.js';
+export { AREA_SCHEMA, resolveArea, areaContains, distanceKm } from './area.js';
+export { LIMIT_SCHEMA, DEFAULT_LIMIT, MAX_LIMIT, capRows } from './results.js';
+export { createGeocodePlaceService, placeFromGeocodeResult } from './places.js';
+
+/** Every query Core defines, in a stable order. */
+export const coreTools = Object.freeze([
+  getEarthquakes,
+  getActiveFires,
+  getRecentLaunches,
+]);