Skip to main content
Glama

Get Entry by ID

get_entry_by_id
Read-onlyIdempotent

Retrieve 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

NameRequiredDescriptionDefault
entry_idNoThe numeric ID of the entry to retrieve
use_test_dbNo
workspace_idNoOptional 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_numberNo
include_relationshipsNoIf true, includes all linked relationships (causal, related) in the response

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
entryNo
errorNoHuman-readable error message
detailsNoAdditional error context
successNo
categoryNoError category (validation, query, connection, internal)
importanceNo
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
relationshipsNo
aggregated_errorsNoDetails of individual errors in a multi-step operation
importanceBreakdownNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv9.1.0
    • addedOutput schema / properties / importanceBreakdown / additionalProperties
      Added value: +false
    • addedOutput schema / properties / importanceBreakdown / properties
      Added value: +{
      +  "causal": {
      +    "type": "number"
      +  },
      +  "recency": {
      +    "type": "number"
      +  },
      +  "relationships": {
      +    "type": "number"
      +  },
      +  "significance": {
      +    "type": "number"
      +  },
      +  "trustModifier": {
      +    "type": "number"
      +  }
      +}
    • addedOutput schema / properties / importanceBreakdown / required
      Added value: +[
      +  "significance",
      +  "relationships",
      +  "causal",
      +  "recency"
      +]
    • addedOutput schema / properties / importanceBreakdown / type
      Added value: +"object"
    • addedOutput schema / properties / relationships / items
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "aggregated_errors": {
      +      "description": "Details of individual errors in a multi-step operation",
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "message": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "message"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "category": {
      +      "description": "Error category (validation, query, connection, internal)",
      +      "type": "string"
      +    },
      +    "code": {
      +      "description": "Error code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)",
      +      "type": "string"
      +    },
      +    "createdAt": {
      +      "type": "string"
      +    },
      +    "description": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "details": {
      +      "additionalProperties": {},
      +      "description": "Additional error context",
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "error": {
      +      "description": "Human-readable error message",
      +      "type": "string"
      +    },
      +    "fromEntryId": {
      +      "type": "number"
      +    },
      +    "id": {
      +      "type": "number"
      +    },
      +    "recoverable": {
      +      "description": "Whether the error is recoverable",
      +      "type": "boolean"
      +    },
      +    "relationshipType": {
      +      "type": "string"
      +    },
      +    "suggestion": {
      +      "description": "Suggested fix for the error",
      +      "type": "string"
      +    },
      +    "toEntryId": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "fromEntryId",
      +    "toEntryId",
      +    "relationshipType",
      +    "createdAt"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / relationships / type
      Added value: +"array"
  2. First observedv9.0.0

TDQS

C2.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — it does not mention the default inclusion of relationships, the workspace-fallback behavior on RESOURCE_NOT_FOUND, or test-database targeting, all of which materially affect the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler, so there is no wasted wording. Its brevity is a problem of substance rather than of structure, which is captured in the other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters, two undocumented ones, and a workspace/global-fallback gotcha spelled out in the schema, the description is far too thin. An output schema exists, so return values need not be explained, but the lookup semantics and failure handling should have been surfaced.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 60%: entry_id, workspace_id, and include_relationships are documented, but use_test_db and project_number are undocumented in both places. The description compensates for none of this and mentions no parameter behavior at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb ('Retrieve') and a resource ('a specific entry'), so the core operation is inferable. However, it is essentially a rewording of the tool name 'get_entry_by_id' and adds no distinguishing detail versus siblings such as search_entries, get_recent_entries, or team_get_entry_by_id.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool rather than search_entries, search_by_date_range, or get_recent_entries, and no mention of prerequisites. The agent must infer selection criteria entirely from the name and schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools