Skip to main content
The 3ngram MCP server exposes the following actions tools. Every entry is generated from the tool’s source signature and docstring, so this page never drifts from the backend.
Required parameters are marked with the required attribute. Optional parameters show their default value.

​
cancel_action

Cancel Pending Action · writes · destructive · idempotent · closed-world Cancel and discard a pending proposed action (teardown for propose_action). Permanently removes a pending_actions row that is still awaiting a decision, so a proposal that should not be approved leaves no residue. Owner-scoped: a caller can only cancel their own pending actions. Already approved, rejected, executed, or failed actions cannot be cancelled — those are terminal states with audit value; use the approval flow for pending actions you want to reject and record. Returns: str Source: backend/src/engram/mcp/tools/actions.py

​
Parameters

​
action_id
str
required
UUID of the pending action to discard.

​
propose_action

Propose Action · writes · non-destructive · non-idempotent · closed-world Propose an external action (GitHub comment, Linear close, etc.) for user approval. The agent cannot self-execute — the action stays ‘pending’ until an authenticated user approves it via the pending-action approval endpoint. Returns: str Source: backend/src/engram/mcp/tools/actions.py

​
Parameters

​
action_type
str
required
Type of action (e.g., ‘github_comment’, ‘linear_close’)
​
target_provider
str
required
Provider name (‘github’, ‘linear’)
​
target_ref
str
required
Provider-specific reference (e.g., ‘owner/repo#123’)
​
payload_json
str
required
JSON string with action-specific data
​
reason
str
required
Why this action is being proposed
​
source_memory_id
int | None
default:"None"
Optional memory ID that triggered this action