Skip to main content
These flows keep calls small and deterministic. Link out to details in MCP Tools when you need parameters.

​
1) Find a specific entity, then explain it

  1. capsulate:search with type="entity" and a keyword (merchant, order number, tracking number).
  2. capsulate:fetch for the selected entity:* id.
  3. If the user asks “where did this come from?”, follow the linked messages and use capsulate:fetch for message:*.

​
2) Find the right canvas/pattern for a question

  1. capsulate:canvases_list or capsulate:patterns_list for a quick inventory.
  2. capsulate:search with type="canvas" or type="pattern" when you need keyword-based lookup.
  3. capsulate:fetch for the selected canvas:* or pattern:* id to confirm scope.

​
3) Determine which fields you can group/measure

  1. capsulate:records_schema with a canvas_id (or pattern_id).
  2. Pick a group_field (categorical) and optionally a metric_field (numeric).

​
4) List logical records for a Canvas

  1. capsulate:records_find with canvas_id and optional typed field filters.
  2. Select only the fields needed and keep the initial limit small.
  3. Use capsulate:record_get for a specific stable record_id.

​
5) Trend over time

  1. capsulate:records_timeseries with a canvas_id or pattern_id.
  2. Start with interval="month" and no metric_field (count), then add metric_field (sum/avg) if needed.

​
6) Top groups (e.g., merchants, statuses, categories)

  1. capsulate:records_aggregate with group_field and optional metric_field.
  2. Add a date range to answer “in the last 30 days”.

​
7) Jump from an email to structured data

  1. capsulate:search with type="message" for the message.
  2. capsulate:fetch for message:* to get linked entity IDs.
  3. capsulate:bulk_fetch for those entities (and optionally expand related data).

​
8) Get the full context for an evolving event

  1. capsulate:fetch for thread:*.
  2. Summarize the sequence of messages; fetch specific message:* records if the user needs details.

​
9) Reduce tool calls with batching

Use capsulate:bulk_fetch when you already have many IDs (entities/messages) and want details in one response.