Get Entry by ID
get_entry_by_idRetrieve a specific journal entry by its ID to access stored project memory, including linked causal and related relationships for context-aware development.
Instructions
Retrieve a specific entry by its ID
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_entry_by_id"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| entry_id | No | The numeric ID of the entry to retrieve | |
| use_test_db | No | ||
| workspace_id | No | Optional workspace isolation identifier (e.g. "alpha"). Do not use numeric project IDs or "workspace" as the key. [ANTI-HALLUCINATION] If an entry returns RESOURCE_NOT_FOUND, it might belong to another workspace. Set workspace_id: "*" to search globally. | |
| project_number | No | ||
| include_relationships | No | If true, includes all linked relationships (causal, related) in the response |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | Error code (e.g. VALIDATION_ERROR, INTERNAL_ERROR) | |
| entry | No | ||
| error | No | Human-readable error message | |
| details | No | Additional error context | |
| success | No | ||
| category | No | Error category (validation, query, connection, internal) | |
| importance | No | ||
| suggestion | No | Suggested fix for the error | |
| recoverable | No | Whether the error is recoverable | |
| relationships | No | ||
| aggregated_errors | No | Details of individual errors in a multi-step operation | |
| importanceBreakdown | No |