Tool reference · Tasks, workflows & decisions
save_intent
Stores one user prompt in the intents log, the same log the prompt hook writes to.
local stdio server writes
When to use
- You are importing past prompts from another tool.
- Your client has no prompt hook and you want prompts recorded anyway.
- You are seeding test data for list_intents or search_intents.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
promptrequired | string | — | User prompt text as submitted |
session_id | string | — | Session id (defaults to current MCP session) |
project | string | — | Project slug |
Example
Arguments
{
"prompt": "Why does the nightly export job time out?",
"session_id": "sess_2026_09_25_a",
"project": "reporting"
}Result shape
{
"saved": true,
"id": 1307
}The same prompt in the same session within 5 minutes returns the existing id. An empty prompt returns saved: false, id: 0.
Values are illustrative; the keys follow the server's handler. MCP clients receive the result as JSON text content.
Server description
The description the server sends to your agent in tools/list, captured from the v14.7.0 source:
Persist one user prompt into the `intents` table (same source as the UserPromptSubmit hook). Use when programmatically seeding intents — the hook covers normal interactive usage. Dedupes same prompt within 5 min per session.