Reference

Examples

Five things you can try, each carrying what supports it: two that run in this page, two that replay a real recording, and one that is honestly labelled as not existing yet.

AVAILABLEWritten and covered by tests — not yet observed in a live runDeskworth · published · updated · 4 sources · Deskworth OS 0.0.23

Shipped in the current build. You can do this on your own machine today.

A demonstration is worth exactly what supports it. Each of the five below carries its own label, and the labels are not decoration: one of them says the thing does not exist.

  • AVAILABLELIVERuns in your browser, on data derived from the core registry at build time. Nothing is sent anywhere — this site has no tool server to call, and no business calling one.
  • VERIFIEDVERIFIED REPLAYA real recording, dated, replayed. The stream a CLI actually produced, or a capture sealed against a named build.
  • PLANNEDPREVIEWThe shape a thing would take if it existed. Shown as a shape, never as a command you can paste.

#Why nothing here calls a real server

The tool server binds the loopback address of the machine running Deskworth, and every call carries a token issued to one card. A web page has neither. Building a hosted demonstration endpoint would mean running a desk somewhere other than your machine, which is precisely the arrangement this product refuses.

So the live demonstrations do the honest version of the same thing: they build the exact request from the tool’s own declared schema, and show it to you. What you read is what a client would send 4. Whether the answer comes back is a question for your own machine.

#What the replays are made of

  • The desk replay is the recorded stream of a real run, kept in the application’s own fixtures alongside the plan its router produced. The lines carrying absolute paths never leave the machine they were recorded on.
  • The mandate room replays sealed captures of the application, listed in a manifest that names the build they were taken from 3.
  • Mandates without a sealed capture say so on their own page. Borrowing another mandate’s screen would be the cheapest possible lie, and the one hardest to notice.

#The demonstrations

INTERACTIVE DEMO

Compose a tool call

Pick a tool, fill its parameters, and read the exact request a client would send — built from the tool’s own declared schema.

Reads real candles from Yahoo Finance and returns the resolved company name and exchange alongside the series, so a ticker without its venue cannot silently become another company.

Market data · requires Ohlcv · 3 roles hold it

symbol · interval · range — required by the schema, and the call would be refused without them

What a client would send

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "ohlcv",
    "arguments": {}
  }
}

Nothing is sent. This page has no tool server to call — the server binds the loopback address of the machine running Deskworth, and every call carries a token issued to one card.

The tool list, the parameters and which are required are mirrored from the core registry at build time. Nothing is sent anywhere: this page has no tool server to call, and would not be allowed to reach one.

INTERACTIVE DEMO

What a role may call

Choose a mandate and see the tools it holds — and, just as usefully, the ones it is refused.

Declares Desk · Dossier · DossierLu

Can call — 4

  • dossier_contributeDossier
  • pilot_observedDossier
  • dossier_statusDossierLu
  • report_blockedno capability

Refused — 28

  • ohlcvOhlcv
  • vendor_barsOhlcv
  • options_chainOhlcv
  • crypto_quoteOhlcv
  • symbol_searchInstruments
  • macro_seriesMacro
  • vintage_seriesMacro
  • euro_seriesMacro
  • github_repoFilings
  • filing_segmentsFilings
  • filingsFilings
  • offeringsFilings
  • wireWeb
  • web_searchWeb
  • vol_surfaceOhlcv
  • news_openWeb
  • chart_openOhlcv
  • chart_indicatorsOhlcv
  • placeOhlcv
  • broadcastWeb
  • annotateOhlcv
  • dossier_publishBundle
  • workbook_createWorkbook
  • deck_createDeck
  • bundle_createBundle
  • memo_createMemo
  • python_runExecute
  • pilot_actPilote

A refused tool does not appear in that role’s listing at all. It is not shown as a locked door — it does not exist for that role.

Crossed from the capabilities each role declares in its own file with the capability each tool requires. It is the same table the tool server itself enforces, not a second one written for the page. Nothing is sent: the crossing happens in your browser, on data mirrored at build time.

VERIFIED REPLAY

One mission, chapter by chapter

Read what a desk established on a real question — the mandate, the evidence, the controls, and the deliverables it did not produce.

Every line carries its release, its product commit, the kind of evidence behind it, a source you can re-read and a date. Figures come from a dated handover report, from a core registry read at a pinned commit, or from a recorded test you can re-run — never from a summary written for this page.

Open it

VERIFIED REPLAY

One mandate at work

Open a mandate and see what it reads, what it produces, and how it rejoins the desk.

Sealed captures of the application, taken from a named build and listed in a manifest. Mandates without a sealed capture say so on their own page instead of borrowing someone else’s screen.

Open it

#Sources

  1. The tool registry, mirrored on this siteDeskworthinternal registry · tool registry mirror of mcp::tools::TOOLS, crossed with the roles’ declared capabilities · read 2026-09-10Internal document, not published
  2. Deskworth OS — product state at 0.0.23Deskworthinternal handover report · Deskworth OS 0.0.23 · commit produit 5968ef0 · lu à bcae42d · published 2026-09-10 · read 2026-09-10Internal document, not published
  3. The screenshot bench manifestDeskworthinternal registry · sealed against Deskworth OS 0.0.15, commit 923fce3 · published 2026-09-08 · read 2026-09-10Internal document, not published
  4. Model Context Protocol — ToolsModel Context Protocol projectofficial documentation · revision 2026-07-28 · published 2026-07-28 · read 2026-09-10https://modelcontextprotocol.io/specification/2026-07-28/server/tools