Skip to main content
Glama

Manawa Terminal

Get journal entry

get_journal_entry
Read-only

Get a full generated journal entry by ID from list_journal.

Draft ids from submit_journal_draft are not readable until end-of-day
generation; use list_journal after the daily run for valid entry ids
(integer or legacy UUID).

Args:
    entry_id: Journal entry id from list_journal (integer or UUID)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entry_id": "<entry_id>"
    },
    "name": "get_journal_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idYes
strategy_idNoStrategy this call belongs to. UUID from list_strategies. The card this call writes keeps that id. Omit when the call is not part of a strategy.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / strategy_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Strategy this call belongs to. UUID from list_strategies. The card this call writes keeps that id. Omit when the call is not part of a strategy.",
      +  "title": "Strategy Id"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds non-obvious behavioral context — that draft ids fail until EOD generation, implying failed lookups rather than empty results — which annotations cannot express. It does not describe error semantics precisely (what a rejected draft id returns), keeping it below 5.

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?

Two tight sentences front-load the action and the id-source precondition, with the constraint before the args block. The "Args:" section is partly redundant with the schema's required entry_id, but it is short and the substance earns its place.

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

Completeness5/5

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

An output schema exists, so return shape need not be explained. The one thing an agent could get wrong — passing a draft id — is called out with the fix, and the id format ambiguity (integer vs legacy UUID) is resolved. Adequate for a two-parameter read tool.

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

Parameters4/5

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

Schema coverage is 50%: entry_id has no schema description but is documented here as coming from list_journal and accepting integer or legacy UUID, which is the meaningful detail. The optional strategy_id is never mentioned in the description, leaving half the parameter surface to a schema entry that reads as boilerplate from another tool.

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

Purpose5/5

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

States a specific verb and resource ("Get a full generated journal entry by ID") and immediately attributes the id source to list_journal, distinguishing it from sibling list_journal and from submit_journal_draft. An agent can tell exactly what this returns versus the list tool without opening the schema.

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

Usage Guidelines5/5

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

Explicitly states the precondition (ids must come from list_journal) and the negative case (draft ids from submit_journal_draft are unreadable until the end-of-day generation), plus the remedy (use list_journal after the daily run). This is a genuine when-to-use / when-not-to-use pair with a named alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources