ai.zerowidth/caliper

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

Au dernier audit MCP Hub, le serveur MCP « ai.zerowidth/caliper » 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 45 outils

• caliper_datasets_add_items≈ 814 tokens

  Appends items to an existing dataset — use this to grow coverage (new edge cases, scenarios from a completed interview) instead of creating a parallel dataset. Same four shapes as caliper_datasets_create (Q&A, chat, sequence, simulated). Existing items and their ratings are untouched.

  Paramètres, retour & exemple (4)

  Paramètres

  • items · array · requis
    Items to append (1-100).
  • datasetId · string · requis
    Id of the dataset to extend.
  • 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.

  Exemple d'appel

  {"name": "caliper_datasets_add_items", "arguments": {"items": [], "datasetId": "texte"}}

  Exemple de retour

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

• caliper_datasets_create≈ 1146 tokens

  Creates a dataset of test items — THE FIRST STEP of setting up evaluation for a flow. Four item shapes: Q&A (input + optional expectedOutput, the golden answer); CHAT (messages: the conversation so far as role/content user and assistant messages you write, ending on a user message, + expectedResponse for the next reply; the flow writes only that reply, so every earlier assistant turn stays fixed; THE shape for an agent's conversation, built up by depth: a greeting alone, then two messages, then four, each item testing one more reply with the earlier ones baked in); SEQUENCE (turns: 2-20 scripted user messages the model answers one at a time with its own earlier replies in front of it, + expectedResponse for the final reply, optional expectedBehavior for the whole conversation); SIMULATED (goal + optional persona/disposition/strategy/maxTurns + expectedBehavior; a platform flow plays a person adaptively, Caliper-run evals only; disposition is a preset id like genuine, pressure, confused, impatient, or free text). Use sequences and simulated items for the slow attacks and for real customers with real needs: a model that holds on message one often folds on message ten. Write good inputs from real usage: the Compass pages the flow was built from are the best source of realistic scenarios.

  Paramètres, retour & exemple (6)

  Paramètres

  • items · array · requis
    Test items (1-100).
  • title · string · requis
    Dataset name (2-120 chars).
  • 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.
  • visibility · string · optionnel · PRIVATE | WORKSPACE | SHARED
    Who can see it: PRIVATE (only the user), WORKSPACE (every member, the default), or SHARED (specific people, granted afterwards). Say 'make it private' → PRIVATE.
  • description · string · optionnel
    What this dataset covers.

  Exemple d'appel

  {"name": "caliper_datasets_create", "arguments": {"items": [], "title": "texte"}}

  Exemple de retour

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

• caliper_datasets_delete≈ 259 tokens

  Deletes a dataset. Evals bound to it stop being runnable (their binding shows datasetOk: false), and reviews/specs over its items lose their source — check caliper_evals_list for evals that reference it and say so before proposing. May return `needs_confirmation`.

  Paramètres, retour & exemple (3)

  Paramètres

  • datasetId · string · requis
    Dataset id, from caliper_datasets_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 response. Omit on the first call.

  Exemple d'appel

  {"name": "caliper_datasets_delete", "arguments": {"datasetId": "texte"}}

  Exemple de retour

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

• caliper_datasets_generate≈ 967 tokens

  Creates a NEW dataset of model-written items — Q&A by default, or scripted sequences / simulated people via `shape` — pass flowId and the generator reads the flow's prompt, mode, and schema to write realistic cases for THAT flow; `description` adds guidance (or stands alone when there's no flow). Use this when the user wants test cases fast and has none; prefer caliper_datasets_create with hand-written items when real scenarios are already in hand (Compass pages, a transcript). This SPENDS workspace inference credit (one generator call), so it sits behind the approval gate: say so and expect `needs_confirmation`. Returns the dataset summary; read the items with caliper_datasets_get and tell the user to review them before trusting an eval built on them.

  Paramètres, retour & exemple (13)

  Paramètres

  • count · integer · optionnel
    Items to generate, 1-50. Default 10.
  • shape · string · optionnel · qa | sequence | simulated
    What each generated item is: `qa` (one input, the default), `sequence` (2-6 scripted user turns the model answers one at a time, with expectedResponse + expectedBehavior), or `simulated` (a person Caliper plays adaptively: goal, persona, disposition, expectedBehavior). outputsMode applies to `qa` only.
  • title · string · requis
    Dataset name.
  • flowId · string · optionnel
    Workbench flow to generate cases for (from workbench_flows_list). Required unless description is given.
  • presetId · string · optionnel · blank | adversarial | prompt-injection | jailbreak | multilingual
    Framing preset. Default `blank`; the others bias every item toward that attack class.
  • 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.
  • visibility · string · optionnel · PRIVATE | WORKSPACE | SHARED
    Who can see it: PRIVATE (only the user), WORKSPACE (every member, the default), or SHARED (specific people, granted afterwards). Say 'make it private' → PRIVATE.
  • description · string · optionnel
    What the target system does / what to cover. Required (≥10 chars) when flowId is omitted; optional guidance otherwise.
  • disposition · string · optionnel
    With shape `simulated`: how every generated person behaves — a preset id (genuine, pressure, confused, impatient, vague, non-native) or free text. Omit to let the generator vary it from person to person.
  • outputsMode · string · optionnel · none | expected | captured
    What each generated item carries beyond the input: `expected` (golden answers — eval-ready, the default), `none` (inputs only — for a spec others fill in), `captured` (sample answers to rate in a review).
  • expectedStyle · string · optionnel · verbatim | conditions
    With outputsMode `expected`: `verbatim` literal reference answers (default) or `conditions` — what a correct answer must do, when there's no single right wording.
  • datasetDescription · string · optionnel
    Description stored on the dataset.

  Exemple d'appel

  {"name": "caliper_datasets_generate", "arguments": {"title": "texte"}}

  Exemple de retour

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

• caliper_datasets_generate_items≈ 733 tokens

  Appends model-written items to an EXISTING dataset, in the style of what's already there (existing items are the few-shot examples; the output shape matches theirs unless overridden). Use to widen coverage when the user says 'more like these' or 'add edge cases'; write them by hand with caliper_datasets_add_items when the scenarios are known. SPENDS workspace inference credit, so it sits behind the approval gate — say so. Existing items and their ratings are untouched.

  Paramètres, retour & exemple (10)

  Paramètres

  • count · integer · optionnel
    Items to add, 1-20. Default 5.
  • shape · string · optionnel · qa | sequence | simulated
    What each generated item is: `qa` (one input, the default), `sequence` (2-6 scripted user turns the model answers one at a time, with expectedResponse + expectedBehavior), or `simulated` (a person Caliper plays adaptively: goal, persona, disposition, expectedBehavior). outputsMode applies to `qa` only.
  • datasetId · string · requis
    Dataset to extend, from caliper_datasets_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 response. Omit on the first call.
  • description · string · optionnel
    What to bias toward, e.g. 'angry customers', 'ambiguous refund questions'.
  • disposition · string · optionnel
    With shape `simulated`: how every generated person behaves — a preset id (genuine, pressure, confused, impatient, vague, non-native) or free text. Omit to let the generator vary it from person to person.
  • outputsMode · string · optionnel · none | expected | captured
    What each generated item carries beyond the input: `expected` (golden answers — eval-ready, the default), `none` (inputs only — for a spec others fill in), `captured` (sample answers to rate in a review).
  • anchorItemId · string · optionnel
    An item id (from caliper_datasets_get) the new items should resemble most.
  • expectedStyle · string · optionnel · verbatim | conditions
    With outputsMode `expected`: `verbatim` literal reference answers (default) or `conditions` — what a correct answer must do, when there's no single right wording.

  Exemple d'appel

  {"name": "caliper_datasets_generate_items", "arguments": {"datasetId": "texte"}}

  Exemple de retour

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

• caliper_datasets_get≈ 320 tokens

  One dataset with a page of its items — read this BEFORE editing items (caliper_datasets_update_item needs the item id) and before extending coverage, so you don't add cases that already exist. Items come `limit` at a time (default 25) from `offset`; `total` is the full count. Long fields are cut at ~800 characters with a truncation marker. Get the datasetId from caliper_datasets_list.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
    Items per page, 1-100. Default 25.
  • offset · integer · optionnel
    Items to skip. Default 0.
  • datasetId · string · requis
    Dataset id, from caliper_datasets_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": "caliper_datasets_get", "arguments": {"datasetId": "texte"}}

  Exemple de retour

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

• caliper_datasets_list≈ 155 tokens

  Lists datasets in the active workspace. Returns summaries (id, name, item count); items are not included.

  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": "caliper_datasets_list", "arguments": {"workspace": "texte"}}

  Exemple de retour

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

• caliper_datasets_remove_item≈ 262 tokens

  Drops one item. Ratings and run results keyed to it are orphaned (kept in history, gone from the dataset). A dataset must keep at least one item. May return `needs_confirmation`.

  Paramètres, retour & exemple (4)

  Paramètres

  • itemId · string · requis
    Item id, from caliper_datasets_get.
  • datasetId · string · requis
    Dataset id.
  • 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.

  Exemple d'appel

  {"name": "caliper_datasets_remove_item", "arguments": {"itemId": "texte", "datasetId": "texte"}}

  Exemple de retour

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

• caliper_datasets_update≈ 386 tokens

  Changes a dataset's title, description, or visibility. Pass only what changes; items are untouched (use caliper_datasets_add_items / caliper_datasets_update_item / caliper_datasets_remove_item for those). May return `needs_confirmation`.

  Paramètres, retour & exemple (6)

  Paramètres

  • title · string · optionnel
    New name.
  • datasetId · string · requis
    Dataset id, from caliper_datasets_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 response. Omit on the first call.
  • visibility · string · optionnel · PRIVATE | WORKSPACE | SHARED
    Who can see it: PRIVATE (only the user), WORKSPACE (every member, the default), or SHARED (specific people, granted afterwards). Say 'make it private' → PRIVATE.
  • description · ? · optionnel
    New description; null clears it.

  Exemple d'appel

  {"name": "caliper_datasets_update", "arguments": {"datasetId": "texte"}}

  Exemple de retour

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

• caliper_datasets_update_item≈ 858 tokens

  Rewrites one item's content, keeping its id (ratings and eval results keyed to it stay attached). The item's KIND can't change — a Q&A item stays Q&A, a chat item stays chat, a sequence stays a sequence — so pass the same shape you read from caliper_datasets_get. Raw items, and chat items captured with tool calls in them, can't be edited from here. May return `needs_confirmation`.

  Paramètres, retour & exemple (5)

  Paramètres

  • item · object · requis
    The full replacement item, same four shapes as caliper_datasets_create.
  • itemId · string · requis
    Item id, from caliper_datasets_get.
  • datasetId · string · requis
    Dataset id.
  • 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.

  Exemple d'appel

  {"name": "caliper_datasets_update_item", "arguments": {"item": {}, "itemId": "texte", "datasetId": "texte"}}

  Exemple de retour

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

• caliper_evals_create≈ 785 tokens

  Binds a dataset + rubric to something under test as a repeatable eval — THE LAST SETUP STEP before scoring. Two targets: a Workbench flow (pass flowId; Caliper runs inference itself, then caliper_evals_run scores it), or 'external' (target: 'external'; the user's own model runs elsewhere and their script submits outputs through the public API, usually from CI — see the docs guide 'Run evals in CI'). For an external eval, hand back the eval id and tell the user to create a workspace API key with the ci_evals preset in their workspace settings; keys can't be minted from here. flowStage 'draft' evals the live draft (pre-publish); 'published' (default) evals the latest published revision at run time, or one pinned with flowRevisionId. Reuse an existing rubric from caliper_rubrics_list when one already scores this job.

  Paramètres, retour & exemple (13)

  Paramètres

  • title · string · requis
    Eval name (2-120 chars).
  • flowId · string · optionnel
    Workbench flow id to evaluate. Required unless target is 'external'.
  • target · string · optionnel · workbench_flow | external
    'workbench_flow' (default; needs flowId) or 'external' (the user's own model; outputs arrive through the public API).
  • rubricId · string · requis
    Rubric the judge scores with.
  • datasetId · string · requis
    Dataset of test items.
  • flowStage · string · optionnel · draft | published
    Which stage to run against. Use 'draft' while iterating pre-publish. Default 'published'.
  • workspace · string · optionnel
    Workspace slug override.
  • approvalId · string · optionnel
    Approval id from a prior needs_confirmation response. Omit on the first call.
  • scenarioId · string · optionnel
    Workbench-flow evals: run every item as this scenario (one of the flow's, from workbench_flows_scenarios_list), so the flow's variables hold that person's values. A run can pick another with caliper_evals_run's scenarioId. Without one, variables run empty unless an item sets them.
  • visibility · string · optionnel · PRIVATE | WORKSPACE | SHARED
    Who can see it: PRIVATE (only the user), WORKSPACE (every member, the default), or SHARED (specific people, granted afterwards). Say 'make it private' → PRIVATE.
  • description · string · optionnel
  • externalLabel · string · optionnel
    External evals only: what produces the outputs, e.g. 'CI' or 'prod pipeline'. Free text, shown on the eval.
  • flowRevisionId · string · optionnel
    Published-stage evals only: pin to one published revision (id from workbench_flows_revisions_list). Omit to always eval the latest published version at run time.

  Exemple d'appel

  {"name": "caliper_evals_create", "arguments": {"title": "texte", "rubricId": "texte", "datasetId": "texte"}}

  Exemple de retour

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

• caliper_evals_delete≈ 220 tokens

  Deletes an eval and stops its schedule. Run history is kept but no longer reachable from the eval. May return `needs_confirmation`.

  Paramètres, retour & exemple (3)

  Paramètres

  • evalId · string · requis
    Eval id, from caliper_evals_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 response. Omit on the first call.

  Exemple d'appel

  {"name": "caliper_evals_delete", "arguments": {"evalId": "texte"}}

  Exemple de retour

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

• caliper_evals_get≈ 255 tokens

  One eval: what it targets (Workbench flow + stage, or external), its dataset and rubric ids, the rubric criteria it scores with (the snapshot taken at creation), schedule + runOnPublish + regression settings, run counts, latest score, and `binding` health (datasetOk / flowOk false = a run would fail at resolution — say so before proposing caliper_evals_run). Get the evalId from caliper_evals_list or caliper_flow_performance.

  Paramètres, retour & exemple (2)

  Paramètres

  • evalId · string · requis
    Eval id.
  • 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": "caliper_evals_get", "arguments": {"evalId": "texte"}}

  Exemple de retour

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

• caliper_evals_list≈ 165 tokens

  Lists evals in the active workspace with their target config (which Workbench flow, which dataset/rubric). Use to find the evalId for caliper_evals_run.

  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": "caliper_evals_list", "arguments": {"workspace": "texte"}}

  Exemple de retour

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

• caliper_evals_run≈ 417 tokens

  Queues a new run of an eval — inference over the dataset, then LLM-judge scoring. THE VERIFY STEP of the improvement loop: after an approved workbench_flows_edit_text, run the eval again and report the score delta vs the previous run. Runs take a while — but you're brought back into THIS conversation automatically with the scores the moment it finishes, so tell the user it's queued and that you'll follow up here; never poll or ask them to check back. Costs workspace LLM budget, so it sits behind the approval gate: may return `needs_confirmation`.

  Paramètres, retour & exemple (5)

  Paramètres

  • label · string · optionnel
    Short label for the run, e.g. 'after refund-policy fix'.
  • evalId · string · requis
    Eval to run.
  • 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.
  • scenarioId · ? · optionnel
    Run as this scenario instead of the eval's own (one of the flow's, from workbench_flows_scenarios_list); null runs with none. Omit to use the eval's. Running the same eval as two scenarios compares how the flow does for each person.

  Exemple d'appel

  {"name": "caliper_evals_run", "arguments": {"evalId": "texte"}}

  Exemple de retour

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

• caliper_evals_runs_cancel≈ 319 tokens

  Stops a run that is still PENDING / RUNNING / SCORING — the brake on a run that's spending more than expected or was started by mistake. The queue stops at once; an item already handed to the flow finishes on its own timeout. The run settles as FAILED with a 'cancelled' reason and keeps the items it completed. A run that already finished returns run_not_live. May return `needs_confirmation`.

  Paramètres, retour & exemple (4)

  Paramètres

  • runId · string · requis
    Run id, from caliper_evals_run or caliper_evals_runs_list.
  • evalId · string · requis
    Eval the run belongs to.
  • 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.

  Exemple d'appel

  {"name": "caliper_evals_runs_cancel", "arguments": {"runId": "texte", "evalId": "texte"}}

  Exemple de retour

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

• caliper_evals_runs_get≈ 412 tokens

  One run: status, overall score, and by default the ten lowest-scoring items with their per-criterion scores and the judge's reasoning (`items: all` for every item, `none` for totals only). THE ANSWER to 'why did the score drop' — read this, then name the criterion that slipped and quote the reasoning on the lowest items. Works for runs Caliper ran and for runs submitted from CI (triggeredBy 'ci', usually labeled with a pull request number). Still no polling loops; read it when the user asks.

  Paramètres, retour & exemple (5)

  Paramètres

  • items · string · optionnel · worst | all | none
    Which items to include. `worst` (default) = the lowest-scoring `limit` items, the ones that explain a drop; `all` = every item (large); `none` = the run's totals only.
  • limit · integer · optionnel
    How many items for `worst`, default 10.
  • runId · string · requis
    Run id, from caliper_evals_runs_list or caliper_evals_run.
  • evalId · string · requis
    Eval the run belongs to.
  • 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": "caliper_evals_runs_get", "arguments": {"runId": "texte", "evalId": "texte"}}

  Exemple de retour

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

• caliper_evals_runs_item_execution≈ 372 tokens

  What the flow actually DID on one run item: every step in order (what it said, which tools it called with what arguments, what came back) and the final answer, plus status, duration, and cost. Read this when a low score needs explaining beyond the judge's reasoning — a wrong tool call or an empty tool result is usually the cause, and the fix is different from a prompt fix. Pass the run item's `id` (NOT `itemId`) from caliper_evals_runs_get. Items whose outputs were supplied from outside (external evals) have no trace and return not_found. Steps are capped for transport; the run page in Caliper has the full record.

  Paramètres, retour & exemple (4)

  Paramètres

  • runId · string · requis
    Run id.
  • evalId · string · requis
    Eval the run belongs to.
  • runItemId · string · requis
    The run item's `id` from caliper_evals_runs_get (not its dataset itemId).
  • 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": "caliper_evals_runs_item_execution", "arguments": {"runId": "texte", "evalId": "texte", "runItemId": "texte"}}

  Exemple de retour

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

• caliper_evals_runs_list≈ 256 tokens

  Recent runs for one eval, newest first: status (PENDING/RUNNING/SCORING/DONE/FAILED), overall score once DONE, label, and timestamps. THE CHECK-BACK for caliper_evals_run: when the user asks how the run went, read this — cite the run id and score, and compare against the PREVIOUS run's score for the delta. Still don't poll in a loop; check when the user asks or when reporting.

  Paramètres, retour & exemple (2)

  Paramètres

  • evalId · string · requis
    Eval whose runs to 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": "caliper_evals_runs_list", "arguments": {"evalId": "texte"}}

  Exemple de retour

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

• caliper_evals_update≈ 782 tokens

  Changes an eval's title, description, visibility, schedule (interval + time anchor), runOnPublish (queue a run whenever the flow publishes), regressionThreshold (score drop vs the previous run that triggers an alert; null = off), or scenarioId (the scenario runs use). Pass only what changes. The dataset, rubric snapshot, and target are fixed at creation — create a new eval to change those. Scheduled and on-publish runs spend credit on their own, so state that plainly when turning them on. May return `needs_confirmation`.

  Paramètres, retour & exemple (13)

  Paramètres

  • title · string · optionnel
    New name.
  • evalId · string · requis
    Eval id, from caliper_evals_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 response. Omit on the first call.
  • scenarioId · ? · optionnel
    Workbench-flow evals: the scenario every run uses unless a run picks another (one of the flow's, from workbench_flows_scenarios_list); null clears it.
  • visibility · string · optionnel · PRIVATE | WORKSPACE | SHARED
    Who can see it: PRIVATE (only the user), WORKSPACE (every member, the default), or SHARED (specific people, granted afterwards). Say 'make it private' → PRIVATE.
  • description · ? · optionnel
    New description; null clears it.
  • runOnPublish · boolean · optionnel
    Run whenever the targeted flow publishes a version.
  • scheduleTime · ? · optionnel
    Daily/weekly anchor, HH:MM 24-hour in scheduleTimezone. Null = one interval from now.
  • scheduleInterval · ? · optionnel
    Run cadence; null clears the schedule. Each scheduled run spends credit — say so.
  • scheduleTimezone · ? · optionnel
    IANA timezone for scheduleTime, e.g. America/Chicago.
  • scheduleDayOfWeek · ? · optionnel
    Weekly only: 0 = Sunday … 6 = Saturday.
  • regressionThreshold · ? · optionnel
    Score drop vs the previous run that raises an alert, on the 0–1 score scale (0.1 = 10 points); null turns alerts off.

  Exemple d'appel

  {"name": "caliper_evals_update", "arguments": {"evalId": "texte"}}

  Exemple de retour

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

• caliper_flow_performance≈ 306 tokens

  How a Workbench flow is ACTUALLY doing, with receipts: every Caliper eval targeting the flow, recent runs with scores, the latest run decomposed into per-criterion averages, the score delta vs the previous run, and the worst-scoring items WITH the judge's reasoning. Use this BEFORE claiming a flow works or proposing changes — and cite the runId + scores when you do. The worst items are diagnostic: failures clustered around missing company facts suggest a knowledge gap (consider proposing a Compass interview with the workflow owner) rather than a prompt problem.

  Paramètres, retour & exemple (2)

  Paramètres

  • flowId · string · requis
    Workbench flow id to report on.
  • 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": "caliper_flow_performance", "arguments": {"flowId": "texte"}}

  Exemple de retour

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

• caliper_rubrics_create≈ 640 tokens

  Creates the scoring rubric an eval's LLM judge uses — 1-10 criteria, each scored on a numeric scale (default 1-5), judged pass/fail (kind pass_fail), or checked in code with no judge (kind check: contains, not_contains, matches a regex, valid_json, max_chars, equals_expected). Write criteria about the FLOW'S JOB (accuracy to source material, tone, refusal behavior), not generic 'quality'.

  Paramètres, retour & exemple (6)

  Paramètres

  • title · string · requis
    Rubric name (2-120 chars).
  • criteria · array · requis
  • workspace · string · optionnel
    Workspace slug override.
  • approvalId · string · optionnel
    Approval id from a prior needs_confirmation response. Omit on the first call.
  • visibility · string · optionnel · PRIVATE | WORKSPACE | SHARED
    Who can see it: PRIVATE (only the user), WORKSPACE (every member, the default), or SHARED (specific people, granted afterwards). Say 'make it private' → PRIVATE.
  • description · string · optionnel

  Exemple d'appel

  {"name": "caliper_rubrics_create", "arguments": {"title": "texte", "criteria": []}}

  Exemple de retour

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

• caliper_rubrics_delete≈ 226 tokens

  Deletes a rubric. Existing evals keep their snapshot of it and keep running; nothing new can bind to it. May return `needs_confirmation`.

  Paramètres, retour & exemple (3)

  Paramètres

  • rubricId · string · requis
    Rubric id, from caliper_rubrics_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 response. Omit on the first call.

  Exemple d'appel

  {"name": "caliper_rubrics_delete", "arguments": {"rubricId": "texte"}}

  Exemple de retour

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

• caliper_rubrics_get≈ 229 tokens

  One rubric with its criteria — each criterion's name, what the judge looks for, and the score scale. Read this to explain a score (which criterion slipped and what it asks for) or before caliper_rubrics_update. Get the rubricId from caliper_rubrics_list or an eval's rubricId.

  Paramètres, retour & exemple (2)

  Paramètres

  • rubricId · string · requis
    Rubric id.
  • 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": "caliper_rubrics_get", "arguments": {"rubricId": "texte"}}

  Exemple de retour

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

• caliper_rubrics_list≈ 196 tokens

  Lists the rubrics in the active workspace (id, name, description, criterion count). Check here BEFORE caliper_rubrics_create — reuse an existing rubric's id in caliper_evals_create when one already scores the same job. Read a rubric's criteria with caliper_rubrics_get.

  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": "caliper_rubrics_list", "arguments": {"workspace": "texte"}}

  Exemple de retour

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

• caliper_rubrics_update≈ 732 tokens

  Changes a rubric's title, description, visibility, or replaces its criteria wholesale (pass the FULL list — criteria get fresh ids). Evals snapshot the rubric when they're created, so an existing eval keeps scoring with the criteria it started with; say so, and offer to create a new eval when the criteria change materially. May return `needs_confirmation`.

  Paramètres, retour & exemple (7)

  Paramètres

  • title · string · optionnel
    New name.
  • criteria · array · optionnel
    Replacement criteria (1-10) — the whole list, not a diff.
  • rubricId · string · requis
    Rubric id, from caliper_rubrics_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 response. Omit on the first call.
  • visibility · string · optionnel · PRIVATE | WORKSPACE | SHARED
    Who can see it: PRIVATE (only the user), WORKSPACE (every member, the default), or SHARED (specific people, granted afterwards). Say 'make it private' → PRIVATE.
  • description · ? · optionnel
    New description; null clears it.

  Exemple d'appel

  {"name": "caliper_rubrics_update", "arguments": {"rubricId": "texte"}}

  Exemple de retour

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

• caliper_source_feeds_list≈ 220 tokens

  Datasets this source keeps adding to as conversations arrive: which dataset, for what (review, eval, spec), the pick it matches, sampling, how many have landed, and whether it's still running or why it stopped.

  Paramètres, retour & exemple (2)

  Paramètres

  • sourceId · string · requis
    Source id, from caliper_sources_list or search_workspace.
  • 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": "caliper_source_feeds_list", "arguments": {"sourceId": "texte"}}

  Exemple de retour

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

• caliper_source_feeds_stop≈ 264 tokens

  Stops a source from adding new conversations to a dataset. What it already added stays. Get the feedId from caliper_source_feeds_list. May return `needs_confirmation`.

  Paramètres, retour & exemple (4)

  Paramètres

  • feedId · string · requis
    Live dataset id, from caliper_source_feeds_list.
  • sourceId · string · requis
    Source id, from caliper_sources_list or search_workspace.
  • 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.

  Exemple d'appel

  {"name": "caliper_source_feeds_stop", "arguments": {"feedId": "texte", "sourceId": "texte"}}

  Exemple de retour

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

• caliper_sources_list≈ 222 tokens

  Apps sending their agent's traces to Caliper — from their own code, OpenTelemetry, or a published Workbench flow — busiest first: name, how it sends, traces in the last 14 days (per day), and the tools its agent calls most with the share of traces using each. Start here when the user asks how their agent behaves on real traffic; then caliper_sources_over_time for one source.

  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": "caliper_sources_list", "arguments": {"workspace": "texte"}}

  Exemple de retour

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

• caliper_sources_over_time≈ 323 tokens

  One source day by day: traces, failures, tool calls, lookups that found nothing, tokens, cost, and speed (meanMs; p50/p95 as 'answered within' bucket edges); each tool with its calls and the share of each day's traces that used it; the documents lookups landed on most; models used. Use it to answer 'how often is it calling web search and is that changing' — compare the first and last weeks and name the day it moved. Follow with caliper_traces_list on that day or tool to show the conversations behind it.

  Paramètres, retour & exemple (3)

  Paramètres

  • days · integer · optionnel
    How many days back, default 30.
  • sourceId · string · requis
    Source id, from caliper_sources_list or search_workspace.
  • 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": "caliper_sources_over_time", "arguments": {"sourceId": "texte"}}

  Exemple de retour

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

• caliper_sources_to_dataset≈ 618 tokens

  Saves the conversations behind a pick (a day, a tool, a document, failures — the same narrowing as caliper_traces_list) into a new dataset (newDatasetName) or an existing one (datasetId), newest first up to `limit`. `purpose` decides what each item keeps: review = the agent's reply, tool calls included, for people to rate; eval = the reply becomes the expected answer; spec = only the questions, for people to answer. Set keepAdding to make it live: new matching conversations keep arriving (every one, or 1 in 10 / 1 in 100), up to 1,000. Then offer the next step — caliper_evals_create, or a review in Caliper. May return `needs_confirmation`.

  Paramètres, retour & exemple (12)

  Paramètres

  • day · string · optionnel
    One UTC day, YYYY-MM-DD.
  • tool · string · optionnel
    Only traces that called this tool.
  • limit · integer · optionnel
    Most recent N, default 100.
  • purpose · string · requis · review | eval | spec
    review | eval | spec.
  • document · string · optionnel
    Only traces whose lookups hit this document.
  • sourceId · string · requis
    Source id, from caliper_sources_list or search_workspace.
  • datasetId · string · optionnel
    Add to this dataset…
  • 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.
  • errorsOnly · boolean · optionnel
    Only failed traces.
  • keepAdding · ? · optionnel
    Keep adding new matches as they arrive, taking one in this many (1 = every one).
  • newDatasetName · string · optionnel
    …or start one with this name.

  Exemple d'appel

  {"name": "caliper_sources_to_dataset", "arguments": {"purpose": "review", "sourceId": "texte"}}

  Exemple de retour

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

• caliper_starters_install≈ 262 tokens

  Copies one starter into the workspace as a new dataset and a new rubric the user owns and can edit. Returns both ids; the next step is caliper_evals_create binding them to the flow (or target 'external'). Needs caliper:datasets:write and caliper:evals:write.

  Paramètres, retour & exemple (3)

  Paramètres

  • slug · string · requis · prompt-injection | system-prompt-leaking | over-refusal | personal-data | bias-under-ambiguity
    Starter slug from caliper_starters_list.
  • workspace · string · optionnel
    Workspace slug override.
  • approvalId · string · optionnel
    Approval id from a prior needs_confirmation response. Omit on the first call.

  Exemple d'appel

  {"name": "caliper_starters_install", "arguments": {"slug": "prompt-injection"}}

  Exemple de retour

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

• caliper_starters_list≈ 236 tokens

  The starter sets Caliper ships: prompt injection, system-prompt leaking, over-refusal, personal-data handling, bias under ambiguity. Each is a small original dataset (single messages AND multi-turn build-ups: false memory, fabricated earlier turns, slow escalation) paired with an anchored rubric. Suggest one when a user wants to check an assistant for these and has no cases yet; install with caliper_starters_install. Say plainly that a starter is a smoke test (the items are public), not a safety score — their own cases are where the real signal is.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "caliper_starters_list", "arguments": {}}

  Exemple de retour

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

• caliper_traces_get≈ 266 tokens

  One trace: what came in, what went out, and every step in order — model calls (model, tokens, cost, reasoning), tool calls (arguments and result), lookups (query and documents with scores), anything else — each with timing and status. Long values are cut at 2,000 characters. Use it to explain why one conversation went the way it did.

  Paramètres, retour & exemple (3)

  Paramètres

  • traceId · string · requis
    Trace id, from caliper_traces_list.
  • sourceId · string · requis
    Source id, from caliper_sources_list or search_workspace.
  • 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": "caliper_traces_get", "arguments": {"traceId": "texte", "sourceId": "texte"}}

  Exemple de retour

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

• caliper_traces_list≈ 350 tokens

  The traces behind a point on a source's chart, newest first, 50 a page: the question and answer (cut short), tools called, time, tokens, cost, status. Narrow by day, tool, document, or failures; page with `before` (the nextBefore from the last page). Open one with caliper_traces_get.

  Paramètres, retour & exemple (7)

  Paramètres

  • day · string · optionnel
    One UTC day, YYYY-MM-DD.
  • tool · string · optionnel
    Only traces that called this tool.
  • before · string · optionnel
    Paging: the nextBefore from the previous page.
  • document · string · optionnel
    Only traces whose lookups hit this document.
  • sourceId · string · requis
    Source id, from caliper_sources_list or search_workspace.
  • 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.
  • errorsOnly · boolean · optionnel
    Only failed traces.

  Exemple d'appel

  {"name": "caliper_traces_list", "arguments": {"sourceId": "texte"}}

  Exemple de retour

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

• 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": "…"}]}

• 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/caliper