---
title: Operating a store
---

The operate-side tools inspect and operate a live Chronicle system. They are the natural-language equivalent of running the [Cratis CLI](https://github.com/Cratis/cli) against a store: browse the domain, watch observers, read events, and manage jobs. Every tool defaults the event store and namespace to your [configured defaults](/chronicle-mcp/configuration/), so you only name a store or namespace when you want a specific one.

## Capabilities

| Area | Tools | Page |
| ---- | ----- | ---- |
| Exploring the store | `list_event_stores`, `list_namespaces`, `list_event_types`, `list_projections`, `list_read_models`, `get_read_model_instances`, `get_server_version` | [Exploring the store](/chronicle-mcp/operate-side/exploring-the-store/) |
| Events | `get_events`, `get_tail_sequence_number` | [Events](/chronicle-mcp/operate-side/events/) |
| Observer health | `list_observers`, `get_observer`, `list_failed_partitions`, `list_recommendations` | [Observer health](/chronicle-mcp/operate-side/observer-health/) |
| Jobs | `list_jobs`, `get_job`, `get_job_steps`, `stop_job`, `resume_job`, `delete_job` | [Jobs](/chronicle-mcp/operate-side/jobs/) |

## Things to ask

- List all event stores.
- List all event types in the `orders` event store.
- Show me the events for order `8a3f…`.
- Are there any failed partitions?
- What observers use the event type `OrderPlaced`?
- List all jobs, and show me the steps of job `…`.

## Operate-side and design-time together

Operate-side tools discover *what is there*; design-time tools turn that into *artifacts*. A common pattern is to explore event types here, then hand them to [read-model scaffolding](/chronicle-mcp/design-time/read-model-scaffolding/). See [How it works](/chronicle-mcp/concepts/) for the full split.