coulomb/qonto-assistant
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

QONTO-WP-0003-T04: document finance-qonto-read tool profile contract

Browse source 
qonto-assistant's side only, per task scope: the contract a profile named
finance-qonto-read must satisfy in agent-harness (~/agent-harness, ADR-001,
ToolProfile) to reach this MCP surface -- lane (green/blue, never red), the
exact mcp__qonto-assistant__* allowed-tools list, and the optional
finance.qonto.read scope.

Checked agent-harness/agent_harness/profiles.py directly: only CLI-only
profiles exist today (green-commit-only, blue-mail-triage), none grant an
MCP server yet. Included a ready-to-paste ToolProfile entry matching its
actual schema, marked as a proposal for agent-harness's own PR -- not
applied here, since registering it is a separate repo/workplan. Added the
end-to-end example: instance manifest -> harness-injected MCP server config
-> the four allowed tool calls.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-07-23 09:48:36 +02:00
parent b96b8cd5b3
commit 1e476309a3
2 changed files with 103 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

25
workplans/QONTO-WP-0003-mcp-surface.md
View file

@ -175,7 +175,7 @@ headers) listed tools and called `qonto_org_summary` successfully, with
```task
id: QONTO-WP-0003-T04
status: todo
status: done
priority: medium
state_hub_task_id: "c6805812-8419-4200-b4ad-a048a541b3be"
```
@ -191,6 +191,29 @@ callers to present.
Done when: profile contract is documented and referenced from the MCP
integration doc; at least one harness config example uses it end-to-end.
**Done 2026-07-23:** Checked `~/agent-harness` (ADR-001,
`agent_harness/profiles.py`) directly rather than guessing the shape —
`ToolProfile` is real: instances declare a profile by name, the harness
resolves and enforces a hard `--allowedTools` allow-list, instances never
enumerate tools. Today only `green-commit-only` and `blue-mail-triage` are
registered, both CLI-only; no profile currently grants any MCP server.
Added a **`finance-qonto-read`** section to `docs/mcp-integration.md` with
the qonto-assistant-side contract: lane (`green`/`blue` only, never `red`),
the exact `mcp__qonto-assistant__*` allowed-tools list (all four tools,
nothing more), and the optional `finance.qonto.read` required scope. Included
a ready-to-paste proposed `ToolProfile` entry matching agent-harness's actual
`profiles.py` schema, explicitly marked as a proposal for agent-harness's own
PR — **not applied to that repo by this task**, since registering it there is
outside qonto-assistant's scope and a separate repo/workplan. Added the
end-to-end example the done-criteria asks for: an instance manifest
(`tool_profile: finance-qonto-read`) paired with the MCP server config the
harness would inject for that session, showing the full path from profile
name to the four allowed tool calls.
No code changes — this task is qonto-assistant-side documentation only, per
its own scope note. `pytest` → `28 passed` (unchanged).
## Task: Unified audit schema across REST and MCP
```task