Skip to main content
Glama

Manawa Terminal

Submit journal draft

submit_journal_draft

Submit a journal draft for a day. Same-day resubmissions are retained as separate drafts.

The draft is accepted immediately but the readable daily journal entry is
generated automatically at end of day; it then appears in list_journal.
The returned draft id is not a list_journal / get_journal_entry id until then.

Args:
    entry_date: Day the draft is for (YYYY-MM-DD)
    content: Draft text

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_date": "<entry_date>",
      "content": "<content>"
    },
    "name": "submit_journal_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
entry_dateYes
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.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that the write is accepted immediately but the readable entry is generated asynchronously at end of day, and that same-day resubmissions are retained as separate drafts (a real duplication hazard). It also warns that the returned draft id is not a list_journal / get_journal_entry id until generation completes — exactly the kind of ID-mismatch trap an agent would otherwise fall into.

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 core lifecycle and ID caveat are front-loaded in the first three sentences, which is the right ordering. The trailing 'Args:' block partially restates the schema, but it carries genuine format information (YYYY-MM-DD), so little is wasted.

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

Completeness4/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 values need no explanation, yet the description supplies the one thing the schema cannot: the temporal meaning of the returned draft id. Complete for a low-complexity, 3-parameter write tool; the only omission is any mention of the optional strategy_id.

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 description coverage is low (33%), and the description compensates for the two undocumented required params by specifying entry_date's YYYY-MM-DD format and identifying content as the draft text. It says nothing about the optional strategy_id, though the schema itself documents that parameter adequately, so the gap is narrow.

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 ('Submit a journal draft for a day') and immediately clarifies the object's lifecycle relative to the sibling read tools (list_journal, get_journal_entry). An agent can tell this apart from listing or fetching journal entries 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 Guidelines4/5

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

Explains the downstream flow clearly: submit now, the readable entry appears in list_journal at end of day, so an agent knows when to call this versus when to read. It does not state explicit exclusions or name a competing write alternative, but no such sibling exists, and the guidance is otherwise concrete.

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