ai.zerowidth/ledger

Est-ce que ai.zerowidth/ledger est sûr ?

Au dernier audit MCP Hub, le serveur MCP « ai.zerowidth/ledger » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 40 outils

• comments_create≈ 409 tokens

  Posts a comment on a workspace entity — a new thread, or a reply when rootId is given. Use it to leave findings where the discussion already lives (an eval result on the flow being debated, a summary on a long thread). Mention people via mentionedUserIds (from workspace member ids) to ring their notification bell; never mention someone who didn't ask to be pulled in.

  Paramètres, retour & exemple (7)

  Paramètres

  • body · string · requis
  • rootId · string · optionnel
    Reply into this thread; omit to start a new one.
  • entityId · string · requis
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • approvalId · string · optionnel
  • entityKind · string · requis · workbench_flow | compass_page | compass_opportunity | caliper_review | caliper_dataset | caliper_rubric | caliper_eval | caliper_spec
    What the thread hangs on.
  • mentionedUserIds · array · optionnel

  Exemple d'appel

  {"name": "comments_create", "arguments": {"body": "texte", "entityId": "texte", "entityKind": "workbench_flow"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• comments_list≈ 306 tokens

  Lists the comment threads on one workspace entity (open first, then resolved) with authors and timestamps. Read this before weighing in on contested work — the threads are where disagreement lives before it becomes a decision.

  Paramètres, retour & exemple (3)

  Paramètres

  • entityId · string · requis
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • entityKind · string · requis · workbench_flow | compass_page | compass_opportunity | caliper_review | caliper_dataset | caliper_rubric | caliper_eval | caliper_spec
    What the thread hangs on.

  Exemple d'appel

  {"name": "comments_list", "arguments": {"entityId": "texte", "entityKind": "workbench_flow"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• comments_resolve≈ 231 tokens

  Sets a comment thread's resolved state (rootId = the thread's root comment id). Resolve ONLY when the human asked or the thread's question is demonstrably settled — and say what settled it in a reply first. Reopening is for new evidence.

  Paramètres, retour & exemple (4)

  Paramètres

  • rootId · string · requis
  • resolved · boolean · requis
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • approvalId · string · optionnel

  Exemple d'appel

  {"name": "comments_resolve", "arguments": {"rootId": "texte", "resolved": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• entity_tags_browse≈ 258 tokens

  Without a tag: every tag in use across the workspace with how many entities carry it, most-used first — the vocabulary the team already organizes by. With a tag: everything filed under it across every tool, each with its kind, id, title, and path. Use it to reuse existing labels instead of inventing near-duplicates, and to answer 'show me everything about X' when X is a label.

  Paramètres, retour & exemple (2)

  Paramètres

  • tag · string · optionnel
    A tag to expand into its items. Omit to list tags.
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.

  Exemple d'appel

  {"name": "entity_tags_browse", "arguments": {"tag": "texte", "workspace": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• entity_tags_get≈ 352 tokens

  Returns the tags on a batch of entities of one kind — the labels galleries organize by. Ids come from the kind's list/get tool or from search_workspace. Use it before entity_tags_set so you replace the full set knowingly, and to answer 'what is this filed under'. Entities the user can't see are omitted.

  Paramètres, retour & exemple (3)

  Paramètres

  • ids · array · requis
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • entityKind · string · requis · workbench_flow | workbench_task | workbench_kb | compass_page | compass_opportunity | caliper_dataset | caliper_rubric | caliper_eval
    Which kind the ids belong to.

  Exemple d'appel

  {"name": "entity_tags_get", "arguments": {"ids": [], "entityKind": "workbench_flow"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• entity_tags_set≈ 413 tokens

  Replaces the FULL tag set on one entity (an empty list clears it). Read the current tags with entity_tags_get first and pass the merged list — this is not additive. Tags are lowercase letters, numbers, spaces, and hyphens; prefer labels already in use (entity_tags_browse) so the workspace's vocabulary stays small. The id comes from the kind's list/get tool or search_workspace.

  Paramètres, retour & exemple (5)

  Paramètres

  • tags · array · requis
  • entityId · string · requis
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • approvalId · string · optionnel
    Approval id from a prior needs_confirmation response. Omit on the first call.
  • entityKind · string · requis · workbench_flow | workbench_task | workbench_kb | compass_page | compass_opportunity | caliper_dataset | caliper_rubric | caliper_eval

  Exemple d'appel

  {"name": "entity_tags_set", "arguments": {"tags": [], "entityId": "texte", "entityKind": "workbench_flow"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_doc≈ 161 tokens

  Fetch the full Markdown body of a specific docs page by its slug. Use this after `search_docs` when the user needs the complete content of a page. No authentication required.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    Page slug. Accepts 'compass/api', '/compass/api', or 'docs/compass/api'.

  Exemple d'appel

  {"name": "get_doc", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_entries_add_evidence≈ 487 tokens

  Records what happened against an open decision — a manual observation the user reports ('the pilot team says triage feels faster'), an implementation note, or a reference to a Caliper run. Evidence is what settlement later reads, so attach it as it arrives and cite it in the lesson. Metric readings attach themselves via ledger_metrics_record_reading — don't duplicate them here. Fails with conflict on superseded entries. Ids come from ledger_entries_list. May return `needs_confirmation`.

  Paramètres, retour & exemple (7)

  Paramètres

  • data · object · optionnel
    Structured detail worth keeping with the summary.
  • kind · string · optionnel · caliper_eval_run | manual | metric_reading | implementation | task_run | verbatim | source
    Usually `manual`; `caliper_eval_run` with refId for a run; `implementation` when the change shipped.
  • refId · string · optionnel
    Source record id (a Caliper run id, …) when there is one.
  • entryId · string · requis
    The entry the evidence is about.
  • summary · string · requis
    What happened, in one or two sentences.
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • approvalId · string · optionnel
    Approval id from a prior needs_confirmation envelope.

  Exemple d'appel

  {"name": "ledger_entries_add_evidence", "arguments": {"entryId": "texte", "summary": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_entries_create≈ 1320 tokens

  Records a memory entry. Every entry is a TITLE (`summary`: one short plain sentence) over a BODY (`rationale`: the detail, markdown welcome) — never put the detail in the title. Three kinds: `decision` — a change being made now; PRE-REGISTRATION IS THE POINT, so `prediction` (what we expect) must be written NOW, before any evidence exists, and never backfilled to match an outcome. `lesson` — a distilled belief the team already holds (`lesson` text required, no prediction). `observation` — a durable fact worth remembering (no prediction): something already true, never something planned. Ideas, pitches, backlog items, and upcoming work are NOT entries — a dated piece of work that carries out a decision is a plan item (ledger_plan_add on that decision), and a running list you keep across runs belongs in a Napkin doc or sheet. When a user states something durable about their business in conversation, offer to capture it as a lesson or observation. When a user shares MEETING NOTES, propose the decisions you find with ledger_entries_draft so they keep or drop each one in Ledger; use this tool for an entry they've asked you to record. Link the Compass pages the entry touches so future consult-before-acting finds it. May return `needs_confirmation` — summarize the entry and wait for approval.

  Paramètres, retour & exemple (8)

  Paramètres

  • kind · string · optionnel · decision | lesson | observation | belief
    decision = a change with a pre-registered expectation; lesson = a belief arriving already settled; observation = a fact that is already true (not a plan, idea, or pitch).
  • lesson · string · optionnel
    What we learned — required for kind=lesson, optional for kind=observation, forbidden on decisions (their lesson is written at settlement).
  • summary · string · requis
    The entry's TITLE: one short plain sentence naming what we did (decision) or the fact itself (lesson, observation). Plain text, no markdown, at most 280 characters — e.g. "Newsletter moves to a biweekly cadence". Everything longer goes in rationale.
  • rationale · string · optionnel
    The entry's BODY: the detail under the title — why, context, lists, steps. Markdown is fine here and renders as formatted text.
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • approvalId · string · optionnel
    Approval id from a prior needs_confirmation envelope.
  • prediction · object · optionnel
    Decisions ONLY. What we expect: a list of `claims` plus one shared `deadline`, or `freeform` for room decisions nothing can settle. A claim either REACHES a value (comparator + target, e.g. CTA clicks >= 400) or HOLDS one (`hold`, e.g. newsletter reads no more than 5% below the 28 days before this). Name every number the change is expected to move AND every number it shouldn't cost — a decision that claims only what it hopes will rise gets to pick its own evidence. Set `watch: true` on a number worth following that the decision isn't committing to. When the change aims at part of an event metric ("new users in Germany"), narrow the claim with `slice` ({ country: ["DE"] }) using label values from ledger_metrics_get — a claim on an event metric settles on the total counted since landing (reach) or events per day (hold).
  • compassPageIds · array · optionnel
    Where — Compass page ids this decision touches.

  Exemple d'appel

  {"name": "ledger_entries_create", "arguments": {"summary": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_entries_draft≈ 1052 tokens

  Writes up to 50 entries as DRAFTS: proposals that stay out of the record until a person confirms each one in Ledger's Drafts view. Use it for entries you found rather than were told — decisions in meeting notes, or a team's past changes read from its tracker, pull requests or launch posts (set `fromHistory: true`). For history: take each claim from what the source said AT THE TIME, set `landedAt` to when it shipped, attach the source URL, and leave `rollout` as full unless the source says otherwise. These read as low confidence because they were written down after the fact; say so plainly rather than overstating them. Tell the person how many drafts are waiting and that they review them under Decisions → Drafts. May return `needs_confirmation`.

  Paramètres, retour & exemple (4)

  Paramètres

  • drafts · array · requis
  • workspace · string · optionnel
    Workspace slug. Ignored for workspace API keys.
  • approvalId · string · optionnel
  • fromHistory · boolean · optionnel
    True when the drafts come from a team's past work, not the conversation.

  Exemple d'appel

  {"name": "ledger_entries_draft", "arguments": {"drafts": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_entries_get≈ 219 tokens

  One entry's full anatomy — the six fields, attached evidence (Caliper runs, measurements, observations), and the supersede chain (what replaced it, or what it replaced). Cite entry ids when telling the user about prior related decisions.

  Paramètres, retour & exemple (2)

  Paramètres

  • entryId · string · requis
    Entry id (from ledger_entries_list).
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.

  Exemple d'appel

  {"name": "ledger_entries_get", "arguments": {"entryId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_entries_list≈ 521 tokens

  The workspace's memory: decisions (changes with pre-registered expectations), lessons (distilled beliefs), and observations (captured facts). CONSULT BEFORE ACTING — before proposing a flow change, prompt edit, or process decision, filter by the Compass page it touches (compassPageId) and check whether prior attempts exist and how they settled. Filter status=open for unsettled expectations awaiting evidence (each carries a derived `lapsed` flag — true when its deadline has passed; surface lapsed ones when the user asks what needs attention); kind=lesson for what the team already believes.

  Paramètres, retour & exemple (7)

  Paramètres

  • q · string · optionnel
    Free-text search across an entry's summary, rationale, and lesson (case-insensitive). Use it to find the entry about a topic before acting.
  • kind · string · optionnel · decision | lesson | observation | belief
    Filter by species: decision (pre-registered expectations), lesson (distilled beliefs), observation (captured facts).
  • cursor · string · optionnel
    Pagination cursor from a prior page.
  • origin · string · optionnel · manual | workbench | caliper | compass | prism | room | assistant | import
    Filter by who wrote it (manual, workbench, …).
  • status · string · optionnel · draft | open | settled | superseded
    Filter by lifecycle state (open = awaiting evidence).
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • compassPageId · string · optionnel
    Compass page id — every decision touching that workflow / system / person.

  Exemple d'appel

  {"name": "ledger_entries_list", "arguments": {"q": "texte", "kind": "decision", "cursor": "texte", "origin": "manual", "status": "draft", "workspace": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_entries_retract≈ 296 tokens

  Takes an entry out of the curated ledger — THE remedy when you recorded something wrong (a decision that wasn't made, a duplicate, a fact the user corrects). Reversible from Ledger and fully audited, so it is safe to offer as soon as the user says 'that's not right'. Not for overturning a settled claim the team once believed — a human supersedes that. Fails with conflict if already retracted. Ids come from ledger_entries_list. May return `needs_confirmation`.

  Paramètres, retour & exemple (3)

  Paramètres

  • entryId · string · requis
    The entry to retract.
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • approvalId · string · optionnel
    Approval id from a prior needs_confirmation envelope.

  Exemple d'appel

  {"name": "ledger_entries_retract", "arguments": {"entryId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_entries_settle≈ 415 tokens

  The ritual moment: evidence has landed, the expectation closes, the lesson is written. Only propose settlement when attached evidence actually answers the prediction — check `ledger_entries_get` first and cite the evidence in the lesson. `lesson` (what we now believe) is required and permanent; settlement happens exactly once. May return `needs_confirmation`.

  Paramètres, retour & exemple (5)

  Paramètres

  • lesson · string · requis
    What we now believe — the distilled, citable lesson.
  • entryId · string · requis
    The open entry to settle.
  • verdict · string · optionnel · confirmed | mixed | missed
    Did the pre-registered expectation hold? `confirmed` every claim came out as hoped, `missed` none did, `mixed` some did and some didn't. Mixed is not a softer miss — "it worked and it cost us something" is usually the most informative result a change can produce, so use it rather than rounding to either side. Only when the entry carries an expectation and the evidence gives a clear answer.
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • approvalId · string · optionnel

  Exemple d'appel

  {"name": "ledger_entries_settle", "arguments": {"lesson": "texte", "entryId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_entries_update≈ 845 tokens

  Corrects an entry in place — its title (summary), body (rationale), the pre-registered prediction of an OPEN decision (null clears it), or its facet (filing category; editable even after settlement). Works on open decisions, and on lessons, observations, and beliefs (they carry no expectation, so fixing their wording is fine any time). Use to fix a typo, swapped fields, or a misrecorded detail. Never edits kind or lesson. Fails with conflict on a settled decision — its claim is corrected by a human superseding it in Ledger — and on superseded or retracted entries. Entry ids come from ledger_entries_list. May return `needs_confirmation`.

  Paramètres, retour & exemple (7)

  Paramètres

  • facet · ? · optionnel
    Filing facet; empty string = unassigned.
  • entryId · string · requis
    The entry to edit: an open decision, or a lesson / observation / belief.
  • summary · string · optionnel
    New title: one short plain sentence, no markdown, at most 280 characters.
  • rationale · string · optionnel
    New body: the detail under the title; markdown is fine.
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • approvalId · string · optionnel
    Approval id from a prior needs_confirmation envelope.
  • prediction · ? · optionnel
    Replacement expectation (claims + deadline, or freeform), or null to clear it. Correcting a misrecorded expectation is fine; rewriting one to match what happened is not.

  Exemple d'appel

  {"name": "ledger_entries_update", "arguments": {"entryId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_feed_sources_list≈ 190 tokens

  The connected servers this workspace exposes to you, with the id a feed needs. Their tools appear to you namespaced as `ext__<name>__<tool>` — call one directly to see what it returns before proposing a feed. A server the workspace has switched off for you is not listed and cannot be fed from here.

  Paramètres, retour & exemple (1)

  Paramètres

  • workspace · string · optionnel
    Workspace slug. Omit to use the pinned workspace.

  Exemple d'appel

  {"name": "ledger_feed_sources_list", "arguments": {"workspace": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_feeds_backfill≈ 326 tokens

  Run the same frozen instruction over a past range, so a metric has history instead of starting the day it was set up. Offer this whenever you create a feed — a chart with a year behind it is worth far more than one that begins today, and an expectation can be judged against what normal looked like. Works when the source returns a series; a source that only ever reports 'right now' will write one point. Safe to repeat: overlapping ranges dedupe. Keep ranges to a few hundred points; a run that fills up says so. May return `needs_confirmation`.

  Paramètres, retour & exemple (5)

  Paramètres

  • id · string · requis
    Feed id, from ledger_feeds_list.
  • to · string · optionnel
    End of the range. Defaults to now.
  • from · string · requis
    Start of the range, ISO date or instant.
  • workspace · string · optionnel
    Workspace slug. Omit to use the pinned workspace.
  • approvalId · string · optionnel

  Exemple d'appel

  {"name": "ledger_feeds_backfill", "arguments": {"id": "texte", "from": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_feeds_create≈ 546 tokens

  Freeze a tool call as a metric's standing source: it runs on the cadence you give and records what it finds, with no model involved. `metric` takes an id or a snake_case slug; an unknown slug starts tracking that metric. Confirm the mapping with ledger_feeds_preview first. Tell the user they can backfill history afterwards with ledger_feeds_backfill. May return `needs_confirmation`.

  Paramètres, retour & exemple (10)

  Paramètres

  • label · string · optionnel
    Short name for the feed, e.g. "Weekly signups".
  • metric · string · requis
    Metric id, or a snake_case slug to start tracking.
  • mapping · object · requis
  • schedule · object · requis
  • toolArgs · object · optionnel
  • toolName · string · requis
    The tool's own name on that server.
  • workspace · string · optionnel
    Workspace slug. Omit to use the pinned workspace.
  • approvalId · string · optionnel
  • windowHours · integer · optionnel
    How far back each run looks. Sensible per-cadence default.
  • integrationId · string · requis
    From ledger_feed_sources_list.

  Exemple d'appel

  {"name": "ledger_feeds_create", "arguments": {"metric": "texte", "mapping": {}, "schedule": {}, "toolName": "texte", "integrationId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_feeds_delete≈ 188 tokens

  Remove a feed. The readings it already wrote stay — the series is the record and outlives the instruction. Prefer pausing with ledger_feeds_update when the user might want it back. May return `needs_confirmation`.

  Paramètres, retour & exemple (3)

  Paramètres

  • id · string · requis
    Feed id, from ledger_feeds_list.
  • workspace · string · optionnel
    Workspace slug. Omit to use the pinned workspace.
  • approvalId · string · optionnel

  Exemple d'appel

  {"name": "ledger_feeds_delete", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_feeds_list≈ 194 tokens

  The standing instructions for how metrics' numbers arrive — which tool each one calls, how often, and how the last run went. Check before proposing a feed so you don't duplicate one, and consult when a user asks why a metric is stale: a feed with a failing last run is usually the answer.

  Paramètres, retour & exemple (2)

  Paramètres

  • metricId · string · optionnel
    Narrow to one metric (id or slug).
  • workspace · string · optionnel
    Workspace slug. Omit to use the pinned workspace.

  Exemple d'appel

  {"name": "ledger_feeds_list", "arguments": {"metricId": "texte", "workspace": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_feeds_preview≈ 510 tokens

  Call a connected server's tool once and see what a mapping would pull out of the response — nothing is written and no feed is created. Send no `mapping` for a first look: you get a sample of the response plus the paths that hold numbers. Then send a mapping to confirm it finds the readings you expect. Always do this before ledger_feeds_create; proposing a feed whose mapping you haven't seen work is how a metric fills up with the wrong number. May return `needs_confirmation`.

  Paramètres, retour & exemple (7)

  Paramètres

  • mapping · object · optionnel
    How to read the number. Omit on the first look.
  • toolArgs · object · optionnel
    Arguments, exactly as the tool wants them. Use {{from}} / {{to}} (ISO instants) or {{date}} (YYYY-MM-DD) where a time range goes — those are substituted per run, and are what let one feed also backfill.
  • toolName · string · requis
    The tool's own name on that server — NOT the ext__ namespaced form you call it by.
  • workspace · string · optionnel
    Workspace slug. Omit to use the pinned workspace.
  • approvalId · string · optionnel
  • windowHours · integer · optionnel
    How far back the preview's window reaches. Default 24.
  • integrationId · string · requis
    From ledger_feed_sources_list.

  Exemple d'appel

  {"name": "ledger_feeds_preview", "arguments": {"toolName": "texte", "integrationId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_feeds_run≈ 224 tokens

  Run a feed immediately over its own window and record what it finds. Use it right after creating one to prove the mapping works — a run that comes back `empty` names the path that missed, which is what you fix with ledger_feeds_update. Does not move the feed's schedule. Re-running is safe: readings dedupe per time bucket. May return `needs_confirmation`.

  Paramètres, retour & exemple (3)

  Paramètres

  • id · string · requis
    Feed id, from ledger_feeds_list.
  • workspace · string · optionnel
    Workspace slug. Omit to use the pinned workspace.
  • approvalId · string · optionnel

  Exemple d'appel

  {"name": "ledger_feeds_run", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_feeds_update≈ 456 tokens

  Change a feed's arguments, mapping, cadence, or pause it. Reach for this when a feed's last run reports `empty` (the response shape moved, so the mapping needs a new path) or `error`. Changing the mapping changes what the number means, so say what you're changing and why. May return `needs_confirmation`.

  Paramètres, retour & exemple (10)

  Paramètres

  • id · string · requis
    Feed id, from ledger_feeds_list.
  • label · string · optionnel
  • enabled · boolean · optionnel
    false pauses it; the definition and history are kept.
  • mapping · object · optionnel
  • schedule · object · optionnel
  • toolArgs · object · optionnel
  • toolName · string · optionnel
  • workspace · string · optionnel
    Workspace slug. Omit to use the pinned workspace.
  • approvalId · string · optionnel
  • windowHours · integer · optionnel

  Exemple d'appel

  {"name": "ledger_feeds_update", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_metric_presets_adopt≈ 304 tokens

  Creates the named presets as real metrics the workspace owns, tagged from the catalog. Safe to repeat: a preset the workspace already has comes back `already_present` rather than creating a second series, and a workspace's own renames and targets are never overwritten. Adopt only what the user agreed to — a metric nobody reads is noise on the Metrics tab, and eight thoughtful ones beat forty. Tell them the metrics start empty and the next step is a feed (ledger_feeds_create) or a first reading. May return `needs_confirmation`.

  Paramètres, retour & exemple (3)

  Paramètres

  • slugs · array · requis
    Preset slugs from ledger_metric_presets_list.
  • workspace · string · optionnel
    Workspace slug. Ignored for workspace API keys.
  • approvalId · string · optionnel

  Exemple d'appel

  {"name": "ledger_metric_presets_adopt", "arguments": {"slugs": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_metric_presets_list≈ 380 tokens

  Ready-made metrics a business can start tracking, each with a unit, a cadence, which direction is good, a business surface (facet), and cross-cutting tags. Reach for this when a workspace has few or no metrics, when someone asks what they should be measuring, or when a decision needs a number to settle against and none exists. Filter by `facet` (where it lives in the business) or `tag` (what kind of number it is). Suggest a SMALL set — three to six that fit what you know about this business — and say in one sentence why each one, rather than listing the catalog. Adopt with ledger_metric_presets_adopt. These are starting points: a workspace renames and retargets them freely afterwards.

  Paramètres, retour & exemple (2)

  Paramètres

  • tag · string · optionnel · revenue | growth | retention | efficiency | quality | speed | cost | risk
    Cross-cutting bucket, e.g. retention, cost, speed.
  • facet · string · optionnel · product | pricing | gtm | sales | people | ops | tooling | finance
    Business surface, matching the Ledger facet taxonomy.

  Exemple d'appel

  {"name": "ledger_metric_presets_list", "arguments": {"tag": "revenue", "facet": "product"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_metric_starters_adopt≈ 303 tokens

  Creates a starter's metrics at their levels and links them. Pass `slugs` to keep only some of its metrics; links are made only where both ends exist. Safe to repeat and safe after a different starter: metrics the workspace already has are left as they are and get linked into the tree. Adopt only what the user agreed to. Tell them the metrics start empty and the next step is connecting a source (ledger_feeds_create) or a first reading. May return `needs_confirmation`.

  Paramètres, retour & exemple (4)

  Paramètres

  • slugs · array · optionnel
    The starter's metrics to keep. Omit for all of them.
  • starter · string · requis
    Starter slug from ledger_metric_starters_list.
  • workspace · string · optionnel
    Workspace slug. Ignored for workspace API keys.
  • approvalId · string · optionnel

  Exemple d'appel

  {"name": "ledger_metric_starters_adopt", "arguments": {"starter": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_metric_starters_list≈ 226 tokens

  Starter trees by shape of business or team (subscription software, services firm, online store, sales team, service operation). Each lists its metrics with a level (outcome / driver / activity) and the links between them (which number moves which). Reach for this before ledger_metric_presets_list when a workspace has no metrics yet or asks how its numbers fit together: pick the starter that matches what you know about the business, describe its tree in a sentence or two, and offer to adopt it with ledger_metric_starters_adopt, dropping any metric that doesn't fit.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "ledger_metric_starters_list", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_metrics_archive≈ 301 tokens

  Takes a metric out of the gallery (`archived: true`) or puts it back (`false`). Readings stay, and entries that settled against it still read correctly — this is the cleanup for a metric minted once and abandoned, or one the workspace stopped watching. `metricId` accepts the id or slug from ledger_metrics_list. May return `needs_confirmation`.

  Paramètres, retour & exemple (4)

  Paramètres

  • archived · boolean · requis
    true to archive, false to restore.
  • metricId · string · requis
    Metric id or slug (from ledger_metrics_list).
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • approvalId · string · optionnel
    Approval id from a prior needs_confirmation envelope.

  Exemple d'appel

  {"name": "ledger_metrics_archive", "arguments": {"archived": true, "metricId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_metrics_create≈ 598 tokens

  Create a metric — a number the workspace watches (triage time, weekly signups, cost per run). Check ledger_metrics_list first; names are unique per workspace. When a user says they want to track or measure something, offer this. May return `needs_confirmation`.

  Paramètres, retour & exemple (8)

  Paramètres

  • icon · string · optionnel · chart-line | dollar-sign | banknote | landmark | piggy-bank | wallet | coins | receipt
    The thing the number counts, e.g. phone for calls, landmark for profit.
  • name · string · requis
    e.g. "Triage time".
  • unit · string · optionnel
    Display unit — "min", "%", "$", "tickets/day".
  • level · string · optionnel · outcome | driver | activity
    outcome = what the business is judged on; driver = moves an outcome; activity = daily work.
  • drives · array · optionnel
    Ids of existing metrics this one moves.
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • approvalId · string · optionnel
  • description · string · optionnel
    What the number means and where it comes from.

  Exemple d'appel

  {"name": "ledger_metrics_create", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_metrics_get≈ 484 tokens

  One metric's definition (unit, kind, direction, target, cadence) plus its readings newest first and the open decisions bound to it. Use before answering 'how is X trending?' or before recording a reading against it. `metricId` accepts the id or the snake_case slug from ledger_metrics_list. For an event metric whose readings carry labels, `labels` lists each label and its values, largest total first. Pass `slice` to get the series for part of it ("new users in DE"), or `by` to split the series by one label ("new users by country"); either returns `series`, summed per `bucket`.

  Paramètres, retour & exemple (5)

  Paramètres

  • by · string · optionnel
    Event metrics only. A label name to split the series by.
  • slice · object · optionnel
    Event metrics only. Per label, the values to keep: { country: ["DE", "AT"] } keeps readings from DE or AT; several labels must all match. Names and values come from `labels`.
  • bucket · string · optionnel · day | week | month
    Series bucket when `slice` or `by` is set. Default week.
  • metricId · string · requis
    Metric id or slug (from ledger_metrics_list).
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.

  Exemple d'appel

  {"name": "ledger_metrics_get", "arguments": {"metricId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_metrics_list≈ 190 tokens

  The numbers the workspace watches — each with unit, latest reading, and how many open decisions are bound to it. Consult when a user mentions a number that sounds like a tracked metric, and before recording a reading.

  Paramètres, retour & exemple (1)

  Paramètres

  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.

  Exemple d'appel

  {"name": "ledger_metrics_list", "arguments": {"workspace": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_metrics_record_reading≈ 663 tokens

  Record one observation of a tracked metric. `metricId` accepts a metric id OR its snake_case slug from ledger_metrics_list; an unknown one is a not_found error — check ledger_metrics_list, create it with ledger_metrics_create, or pass `createIfMissing: true` to mint a "measure" metric at that slug in the same call (an "event" metric when the reading carries `labels`). The reading automatically lands as evidence on every open decision whose prediction is bound to this metric — so when a user reports a number ("triage is down to 12 minutes"), offer to record it. For event-kind metrics, omit `value` to count one occurrence. May return `needs_confirmation`.

  Paramètres, retour & exemple (9)

  Paramètres

  • at · string · optionnel
    ISO timestamp the reading is for. Defaults to now; set it when backfilling an earlier reading.
  • key · string · optionnel
    Idempotency key (e.g. "2026-w32") — a repeat write with the same key returns the original reading instead of doubling the series. Use for scheduled/recurring recordings. The key is per set of labels, so one key per day can cover every country.
  • note · string · optionnel
    Where the number came from, if worth recording.
  • value · number · optionnel
    The observed value, in the metric's unit. Omit for event-kind metrics to record one occurrence.
  • labels · object · optionnel
    Event metrics only. What this count is broken down by, e.g. { country: "DE", plan: "pro" } — snake_case names, string values. Lets the metric be read and claimed by slice later. Refused on a measure.
  • metricId · string · requis
    Metric id or slug (from ledger_metrics_list).
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • approvalId · string · optionnel
  • createIfMissing · boolean · optionnel
    Mint the metric when the slug is unknown. Default false — an unknown slug is an error, so a typo can't quietly start a second series.

  Exemple d'appel

  {"name": "ledger_metrics_record_reading", "arguments": {"metricId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_metrics_update≈ 857 tokens

  Corrects a metric's name, unit, description, kind (measure / event), direction (which way is good), target, cadence, icon, level, or the metrics it drives (its place in the metric tree). Readings are untouched. Only what you pass changes. The slug is not editable here — external writers address metrics by slug. Fails with conflict when a rename collides with a live metric. `metricId` is the id from ledger_metrics_list. May return `needs_confirmation`.

  Paramètres, retour & exemple (13)

  Paramètres

  • icon · ? · optionnel
    The mark the metric wears in every tool: the thing it counts (phone for calls, landmark for profit). "" goes back to the catalog's icon.
  • kind · string · optionnel · measure | event
    measure = a value each reading; event = a count of occurrences.
  • name · string · optionnel
  • unit · string · optionnel
    "min", "%", "$", "tickets/day".
  • level · ? · optionnel
    outcome = what the business is judged on; driver = a number that moves an outcome; activity = daily work. "" unplaces it.
  • drives · array · optionnel
    Ids of the metrics this one moves. Replaces the current set; pass the full list. Loops are refused.
  • target · ? · optionnel
    Goal value in the metric's unit; null clears.
  • cadence · string · optionnel · | daily | weekly | monthly | quarterly
    How often a reading is expected.
  • metricId · string · requis
    Metric id (from ledger_metrics_list).
  • direction · string · optionnel · up | down | none
    up = higher is better, down = lower is better, none.
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • approvalId · string · optionnel
    Approval id from a prior needs_confirmation envelope.
  • description · string · optionnel

  Exemple d'appel

  {"name": "ledger_metrics_update", "arguments": {"metricId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_plan_add≈ 594 tokens

  Adds a plan item to an OPEN decision (the work that carries it out: a post, a launch step, an email). Omit entryId for a standalone date (a holiday, an event you're only watching). Items are all-day unless you pass startTime with timeZone (and optionally endTime), for a webinar, a scheduled post, or a launch at noon. If the date costs money or time and comes with an expectation, record it as a decision with ledger_entries_create instead. Use repeatWeeklyUntil for a weekly cadence: it writes one row per week (max 60), each movable on its own. Fails with conflict once the decision is settled. May return `needs_confirmation`.

  Paramètres, retour & exemple (13)

  Paramètres

  • url · string · optionnel
    Where the work lives (draft, deck, published post).
  • note · string · optionnel
  • tags · array · optionnel
    What kind of work it is: blog, video, social, event… Reuse the workspace's existing tags (see ledger_plan_list).
  • dueOn · string · requis
    A calendar day, YYYY-MM-DD.
  • title · string · requis
  • endTime · string · optionnel
    Same-day end, after startTime.
  • entryId · string · optionnel
    The open decision this carries out.
  • timeZone · string · optionnel
    IANA zone the time is in (America/Chicago). Required with startTime; use the user's own zone.
  • startTime · string · optionnel
    Omit for an all-day item. 24-hour HH:MM in timeZone.
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • approvalId · string · optionnel
    Approval id from a prior needs_confirmation envelope.
  • ownerUserId · string · optionnel
    A workspace member's user id.
  • repeatWeeklyUntil · string · optionnel
    Also add a copy every 7 days through this day.

  Exemple d'appel

  {"name": "ledger_plan_add", "arguments": {"dueOn": "texte", "title": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_plan_delete≈ 248 tokens

  Removes one plan item while its decision is open, for an item added by mistake or work that's no longer planned. If the work was planned and then dropped, prefer ledger_plan_update with status 'skipped' so settlement can see it. Fails with conflict once the decision is settled. May return `needs_confirmation`.

  Paramètres, retour & exemple (3)

  Paramètres

  • itemId · string · requis
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • approvalId · string · optionnel
    Approval id from a prior needs_confirmation envelope.

  Exemple d'appel

  {"name": "ledger_plan_delete", "arguments": {"itemId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_plan_list≈ 344 tokens

  Pass `entryId` for one decision's plan items, or `from` + `to` (YYYY-MM-DD, at most about a year apart) for the calendar: decision spans (recorded day → expectation deadline) plus every dated item inside the window, including standalone dates with no decision. Filter the calendar by `ownerUserId` to answer 'what's mine this week' or to find tomorrow's items to draft. Never use it to compare or rank people's output.

  Paramètres, retour & exemple (6)

  Paramètres

  • to · string · optionnel
    A calendar day, YYYY-MM-DD.
  • tag · string · optionnel
    Only items with this tag (blog, video, event…).
  • from · string · optionnel
    A calendar day, YYYY-MM-DD.
  • entryId · string · optionnel
    One decision's plan.
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • ownerUserId · string · optionnel
    Only items owned by this member.

  Exemple d'appel

  {"name": "ledger_plan_list", "arguments": {"to": "texte", "tag": "texte", "from": "texte", "entryId": "texte", "workspace": "texte", "ownerUserId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ledger_plan_update≈ 480 tokens

  Edits one plan item while its decision is open: move it (dueOn), rename it, change the owner (null clears), attach the link, or set status (planned | done | skipped). Mark done only when the user says it shipped; a link alone doesn't mean done. Fails with conflict once the decision is settled. May return `needs_confirmation`.

  Paramètres, retour & exemple (13)

  Paramètres

  • url · ? · optionnel
  • note · string · optionnel
  • tags · array · optionnel
    Replaces the item's tags.
  • dueOn · string · optionnel
    A calendar day, YYYY-MM-DD.
  • title · string · optionnel
  • itemId · string · requis
  • status · string · optionnel · planned | done | skipped
  • endTime · ? · optionnel
  • timeZone · ? · optionnel
    Required when setting startTime.
  • startTime · ? · optionnel
    null makes it all-day again.
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
  • approvalId · string · optionnel
    Approval id from a prior needs_confirmation envelope.
  • ownerUserId · ? · optionnel

  Exemple d'appel

  {"name": "ledger_plan_update", "arguments": {"itemId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_docs≈ 156 tokens

  Enumerate all available docs pages, optionally filtered by product (e.g. 'compass', 'legal', 'overview'). Use this to discover what slugs exist before calling `get_doc`. No authentication required.

  Paramètres, retour & exemple (1)

  Paramètres

  • product · string · optionnel
    Optional product slug filter (e.g. 'compass', 'legal', 'overview').

  Exemple d'appel

  {"name": "list_docs", "arguments": {"product": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_docs≈ 226 tokens

  Search ZeroWidth product documentation. Returns matching pages with title, slug, public URL, and a query-relevant snippet. Use this when the user asks about a ZeroWidth product (Compass, Workbench, Caliper, Prism, Ledger, Napkin, zv1), an API behavior, or a policy. No authentication required — the docs corpus is public.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
    Max number of results. Defaults to 10.
  • query · string · requis
    Search query — keywords or natural-language phrase.

  Exemple d'appel

  {"name": "search_docs", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_workspace≈ 670 tokens

  Finds anything in the workspace in one call — uploaded files (searching the text inside them), folders, Workbench flows, shims, knowledge bases and tasks, Compass pages and changes, Caliper datasets, evals, rubrics, reviews, specs and sources, Ledger entries, Napkin sketches, decks, docs, sheets, diagrams and interfaces. The same search the person uses in Home. Use it FIRST whenever the user mentions something without saying where it lives ('the SOW', 'the dispatch interviews', 'that invoice'). The query is words in any order: each word must appear in the thing's name, its tags, the names of the folders it's filed under, or the text inside it — so 'northwind sow' finds the SOW filed in the Northwind folder, and 'dispatch interview' finds 'Dispatcher interview 1.md'. Results are ranked best first. Each hit carries its id, kind, path (for a link), folderPath (where it's filed, top-down), tags, and a snippet when the words were found inside it rather than in its name — say where a thing lives using folderPath. A file's id feeds workspace_files_read; other ids feed the kind's *_get tool. Pass folderId to search only inside one folder and everything under it. If nothing comes back, try fewer or different words before telling the user it doesn't exist. Results only include what the user can see, and only kinds this token may read.

  Paramètres, retour & exemple (5)

  Paramètres

  • q · string · requis
    Words, any order, case-insensitive. Fewer words find more.
  • kinds · array · optionnel
    Restrict to these kinds (file, folder, flow, page, doc, dataset, …). Omit to search everything.
  • limit · integer · optionnel
  • folderId · string · optionnel
    Only search inside this folder and the folders under it (ids from workspace_folders_browse or a folder hit).
  • workspace · string · optionnel
    Workspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.

  Exemple d'appel

  {"name": "search_workspace", "arguments": {"q": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://api.zerowidth.ai/mcp/x/ledger