@stratta/mcp 0.13.1 → 0.15.0

package/README.md

@@ -34,7 +34,7 @@ https://stratta.ch/mcp
 That is the shorter path, the one the dashboard walks you through for Claude,
 ChatGPT, Claude Code, Codex, Cursor, VS Code, Gemini CLI and Windsurf, and the
 only one that works in an agent running in the cloud (claude.ai, ChatGPT). It
-serves 35 of the 36 tools below, **ingestion included**: the pre-pass script is
+serves 54 of the 55 tools below, **ingestion included**: the pre-pass script is
 downloaded from https://stratta.ch/ingest-prepass.py when it is not on disk.
 See https://stratta.ch/docs/en/guides/connect-remote.
 
@@ -176,8 +176,8 @@ named `E2E dossier <timestamp>` and does not delete it.
 
 ## Tools exposed
 
-36 tools, generated from one catalogue shared with the remote connector (which
-serves the same 33 minus `add_attachment`).
+55 tools, generated from one catalogue shared with the remote connector (which
+serves the same 54, everything minus `add_attachment`).
 
 **Read** (10 tools — query the norms of your workspace):
 
@@ -194,31 +194,50 @@ serves the same 33 minus `add_attachment`).
 | `get_figure`      | Retrieve a figure inline (base64 ImageContent).                                         |
 | `get_cross_refs`  | Outgoing cross-refs from a section to other norms.                                      |
 
-**Site** (3 tools — what public Swiss registers know about a plot):
-
-| Tool               | Purpose                                                                                                                             |
-| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
-| `scan_site`        | Collect municipality, parcel, elevation, geology, nearby boreholes, polluted sites, hazards and noise class around a Swiss address. |
-| `get_site_context` | Read what the scan settled, and — separately — what it could not, with the reason.                                                  |
-| `get_boreholes`    | Read the boreholes nearest the site with their logged strata, SIA 261 ground class, water table, and links to cantonal documents.   |
-
-**Dossier** (13 tools — keep what was decided on a project):
-
-| Tool                | Purpose                                                                                                |
-| ------------------- | ------------------------------------------------------------------------------------------------------ |
-| `list_dossiers`     | Your organisation's dossiers, most recently touched first, with open-question counts.                  |
-| `open_dossier`      | Open a project's dossier, creating it if needed. Idempotent on the name.                               |
-| `open_question`     | Open one question to settle, with optional named options. Idempotent on the title.                     |
-| `save_finding`      | Record one piece of evidence: a cited article, a retained value and why, an observation.               |
-| `record_decision`   | Settle a question with a decision the engineer has confirmed, and the retained option.                 |
-| `load_dossier`      | Reload everything: questions with their evidence and decisions, open ones first.                       |
-| `resolve_question`  | Close a question without a decision, or reopen one. The evidence stays.                                |
-| `list_attachments`  | The project attachments of a dossier: site reports, borehole logs, minutes, data sheets.               |
-| `read_attachment`   | Read an attachment's text as Markdown, page by page.                                                   |
-| `search_in_dossier` | Full-text search over a dossier's attachments, with the page of each hit.                              |
-| `add_attachment`    | Upload a file from the user's machine to a dossier (PDF, DOCX, XLSX, images, text). Local server only. |
-| `list_templates`    | The checklists the organisation wrote for its types of structure.                                      |
-| `apply_template`    | Open a template's questions in a dossier and file the clauses that resolve in the corpus.              |
+**Site** (10 tools — what public Swiss registers know about a plot, and the site sheet as the app shows it):
+
+| Tool                       | Purpose                                                                                                                             |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
+| `scan_site`                | Collect municipality, parcel, elevation, geology, nearby boreholes, polluted sites, hazards and noise class around a Swiss address. |
+| `get_site_context`         | Read what the scan settled, and — separately — what it could not, with the reason.                                                  |
+| `get_boreholes`            | Read the boreholes nearest the site with their logged strata, SIA 261 ground class, water table, and links to cantonal documents.   |
+| `list_sites`               | The site sheets of the organisation, with their dossier, canton and scan status.                                                    |
+| `get_site`                 | The sheet as the app shows it: every fact with its key, status, source, notice and attribution, and the scan with its sources.      |
+| `get_site_section`         | The section along the axis: terrain, modelled bedrock, geology bands and the boreholes of the corridor with their logs.             |
+| `list_site_overlays`       | The map areas around the point (polluted sites, hazards, water protection), with distance and coverage of the site point.           |
+| `get_groundwater_contours` | The cantonal piezometric contours stored by the scan, with the aquifer name and elevation.                                          |
+| `list_site_photos`         | The photos uploaded on the sheet, with position, direction, instant and note. No image, no link.                                    |
+| `list_site_neighbours`     | The organisation's other sheets within a radius, with the distance and the geological unit their scan established.                  |
+
+**Dossier** (25 tools — keep what was decided on a project, and everything the dossier page can do to a question):
+
+| Tool                   | Purpose                                                                                                |
+| ---------------------- | ------------------------------------------------------------------------------------------------------ |
+| `list_dossiers`        | Your organisation's dossiers, most recently touched first, with open-question counts and site id.      |
+| `open_dossier`         | Open a project's dossier, creating it if needed. Idempotent on the name.                               |
+| `open_question`        | Open one question to settle, with optional named options. Idempotent on the title.                     |
+| `save_finding`         | Record one piece of evidence: a cited article, a retained value and why, an observation.               |
+| `record_decision`      | Settle a question with a decision the engineer has confirmed, and the retained option.                 |
+| `load_dossier`         | Reload everything: questions with their evidence and decisions, open ones first.                       |
+| `resolve_question`     | Close a question without a decision, or reopen one. The evidence stays.                                |
+| `list_attachments`     | The project attachments of a dossier: site reports, borehole logs, minutes, data sheets.               |
+| `read_attachment`      | Read an attachment's text as Markdown, page by page.                                                   |
+| `search_in_dossier`    | Full-text search over a dossier's attachments, with the page of each hit.                              |
+| `add_attachment`       | Upload a file from the user's machine to a dossier (PDF, DOCX, XLSX, images, text). Local server only. |
+| `list_templates`       | The checklists the organisation wrote for its types of structure.                                      |
+| `apply_template`       | Open a template's questions in a dossier and file the clauses that resolve in the corpus.              |
+| `list_questions`       | The questions of a dossier, paginated, with status, assignee, due date, options and decision title.    |
+| `get_question`         | One question in full: options, decision, evidence with every citation field, comments with authors.    |
+| `get_dossier_activity` | The history of a dossier, most recent first, paginated: who did what, from the app or an agent.        |
+| `list_exports`         | The verification notes and journals exported from a dossier, with hash and trusted timestamp.          |
+| `update_question`      | Reword a question, assign it by e-mail address, set or clear its due date.                             |
+| `add_option`           | Add one way of settling a question. Idempotent on the name.                                            |
+| `update_option`        | Rename or describe an option, or mark it retained (the others are released).                           |
+| `delete_option`        | Remove an option; its evidence stays on the question. Asks the user first.                             |
+| `delete_question`      | Delete a question opened by mistake; its evidence stays, unfiled. Asks the user first.                 |
+| `add_comment`          | Leave a signed remark on a dossier, a question or an entry.                                            |
+| `update_entry`         | Correct an entry's wording, value, confidence or citation in place.                                    |
+| `attach_entry`         | File an entry under a question and optionally an option, or unfile it.                                 |
 
 A dossier is read, annotated, reviewed and exported from
 [stratta.ch/dossiers](https://stratta.ch/dossiers).

package/dist/confirm.d.ts

@@ -9,7 +9,16 @@ import type { CallToolResult } from '@modelcontextprotocol/sdk/types.js';
  * `confirmed: true` when it does not. The Convex function never sees the
  * difference.
  */
-export declare const CONFIRMED_TOOLS: Record<string, (args: Record<string, unknown>) => string>;
+type Confirmation = {
+    /** What is at stake, as the dialog names it. */
+    what: string;
+    /** The one line the user reads, built from the arguments. */
+    summary: (args: Record<string, unknown>) => string;
+    /** The question asked. A removal never asks "Record it". */
+    prompt: string;
+};
+export declare const CONFIRMED_TOOLS: Record<string, Confirmation>;
 export declare const CONFIRMATION_HINT: string;
 /** `null` when the call may proceed, a tool result to return otherwise. */
 export declare function confirmWithUser(server: Pick<Server, 'getClientCapabilities' | 'elicitInput'>, toolName: string, args: Record<string, unknown>): Promise<CallToolResult | null>;
+export {};

package/dist/confirm.js

@@ -1,32 +1,54 @@
-/**
- * The confirmation step before a decision is written, on stdio.
- *
- * Same contract as the remote gate: `confirmed: true` in the arguments means
- * the agent already asked the user; otherwise the client is asked through an
- * elicitation when it supports one, and told to come back with
- * `confirmed: true` when it does not. The Convex function never sees the
- * difference.
- */
+const decisionSummary = (args) => [
+    args.title,
+    args.value ? `= ${String(args.value)}` : null,
+    args.retainedOption ? `(option ${String(args.retainedOption)})` : null,
+]
+    .filter(Boolean)
+    .map(String)
+    .join(' ');
 export const CONFIRMED_TOOLS = {
-    record_decision: (args) => [
-        args.title,
-        args.value ? `= ${String(args.value)}` : null,
-        args.retainedOption ? `(option ${String(args.retainedOption)})` : null,
-    ]
-        .filter(Boolean)
-        .map(String)
-        .join(' '),
-    resolve_question: (args) => args.resolved === false
-        ? 'reopen this question'
-        : 'close this question without a decision',
+    record_decision: {
+        what: 'Decision',
+        summary: decisionSummary,
+        prompt: 'Record it in the dossier?',
+    },
+    resolve_question: {
+        what: 'Question',
+        summary: (args) => args.resolved === false
+            ? 'reopen this question'
+            : 'close this question without a decision',
+        prompt: 'Record it in the dossier?',
+    },
+    // The two deletions of 0.14.0. The gate only sees ids, so the line says
+    // what goes and what stays rather than naming the row.
+    delete_question: {
+        what: 'Question',
+        summary: () => 'delete this question with its options, its comments and its decision; ' +
+            'its evidence stays in the dossier, unfiled',
+        prompt: 'Delete it?',
+    },
+    delete_option: {
+        what: 'Option',
+        summary: () => 'remove this option; the evidence filed under it stays on the question',
+        prompt: 'Remove it?',
+    },
+    // The third deletion, gated since 0.15.0 on both transports: it is the one
+    // that empties a corpus rather than a dossier.
+    ingest_delete: {
+        what: 'Document',
+        summary: () => 'delete this document with all its sections, figures, tables, formulas ' +
+            'and cross-references; the dossiers that cite it keep their citations, ' +
+            'pointing at a document that no longer exists',
+        prompt: 'Delete it?',
+    },
 };
 export const CONFIRMATION_HINT = 'Not recorded: this client cannot ask the user directly. Confirm the ' +
     'decision with the user in the conversation, then call again with ' +
     'confirmed: true.';
 /** `null` when the call may proceed, a tool result to return otherwise. */
 export async function confirmWithUser(server, toolName, args) {
-    const summary = CONFIRMED_TOOLS[toolName];
-    if (!summary || args.confirmed === true)
+    const confirmation = CONFIRMED_TOOLS[toolName];
+    if (!confirmation || args.confirmed === true)
         return null;
     if (!server.getClientCapabilities()?.elicitation) {
         return {
@@ -37,10 +59,10 @@ export async function confirmWithUser(server, toolName, args) {
     }
     const result = await server.elicitInput({
         mode: 'form',
-        message: `${toolName === 'record_decision' ? 'Decision' : 'Question'}: ${summary(args)}\n\nRecord it in the dossier?`,
+        message: `${confirmation.what}: ${confirmation.summary(args)}\n\n${confirmation.prompt}`,
         requestedSchema: {
             type: 'object',
-            properties: { confirm: { type: 'boolean', title: 'Record it' } },
+            properties: { confirm: { type: 'boolean', title: 'Confirm' } },
             required: ['confirm'],
         },
     });

package/dist/errors.js

@@ -47,6 +47,7 @@ const HELP = {
     RATE_LIMITED: `${DOCS}/resources/troubleshooting`,
     DOSSIER_NOT_FOUND: `${DOCS}/mcp/dossier-tools`,
     DOSSIER_CLOSED: `${DOCS}/guides/suivre-un-projet`,
+    READ_ONLY: `${DOCS}/account/plans`,
     ENTRY_NOT_FOUND: `${DOCS}/mcp/dossier-tools`,
     TOO_MANY_DOSSIERS: `${DOCS}/mcp/dossier-tools`,
     TOO_MANY_ENTRIES: `${DOCS}/mcp/dossier-tools`,
@@ -129,6 +130,45 @@ export function formatToolError(err) {
                         "Cette entrée n'existe pas, ou elle appartient à un autre dossier.",
                         'Rechargez le dossier avec `load_dossier` pour obtenir des identifiants à jour.',
                     ]);
+                case 'QUESTION_NOT_FOUND':
+                    return withHelp(data, [
+                        "Cette question n'existe pas dans votre organisation, ou elle appartient à un autre dossier.",
+                        'Appelez `list_questions` sur le dossier pour obtenir des identifiants à jour.',
+                    ]);
+                case 'OPTION_NOT_FOUND':
+                    return withHelp(data, [
+                        "Cette option n'existe pas, ou elle appartient à une autre question.",
+                        'Appelez `get_question` pour lire les options et leurs identifiants.',
+                    ]);
+                case 'OPTION_WITHOUT_QUESTION':
+                    return withHelp(data, [
+                        'Une option se rattache à une question : donnez `questionId` avec `optionId`.',
+                    ]);
+                case 'DECISION_IS_BOUND':
+                    return withHelp(data, [
+                        'Une décision appartient à sa question et ne se déplace pas. Corrigez-la avec `update_entry`, ou rouvrez la question avec `resolve_question` (resolved: false).',
+                    ]);
+                case 'NOT_A_MEMBER':
+                    return withHelp(data, [
+                        "Cette adresse ne correspond à aucun membre de l'organisation. Demandez à l'utilisateur l'adresse exacte, ou laissez la question sans responsable.",
+                    ]);
+                case 'INVALID_DATE':
+                    return withHelp(data, [
+                        'La date attendue est un jour ISO, par exemple « 2026-10-15 ».',
+                    ]);
+                case 'SITE_NOT_FOUND':
+                    return withHelp(data, [
+                        "Cette fiche de site n'existe pas dans votre organisation.",
+                        'Appelez `list_sites`, ou lisez `siteId` sur la ligne du dossier dans `list_dossiers`.',
+                    ]);
+                case 'TOO_MANY_QUESTIONS':
+                    return withHelp(data, [
+                        'Ce dossier a atteint son plafond de questions. Ne réessayez pas ; closez ou supprimez celles qui ne comptent plus.',
+                    ]);
+                case 'TOO_MANY_OPTIONS':
+                    return withHelp(data, [
+                        'Cette question a déjà dix options, le maximum. Ne réessayez pas ; retirez-en une avec `delete_option` si une nouvelle est nécessaire.',
+                    ]);
                 case 'TOO_MANY_DOSSIERS':
                     return withHelp(data, [
                         'Cette organisation a atteint son plafond de dossiers.',