Skip to main content
Glama

post_gl_journal_entry

Post a draft entry into the books — accountant. One-way.

A posted entry can no longer be replaced or discarded (both refuse with 409); the only general correction is …/reverse, which leaves both the original and the reversal visible. The one exception is PUT …/guessed-account, which re-points a coding_guessed entry's expense account in place — and it works only on a posted entry. Check the draft before posting rather than after.

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": {
      "company_id": "<company_id>",
      "entry_id": "<entry_id>"
    },
    "name": "post_gl_journal_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
entry_idYes
company_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / body / anyOf
      Previous value: -[
      -  {
      -    "description": "Optional body for posting a manual entry.\n\n``allow_untagged_control``: an AR/AP control line with no open item (ZET-150).\n``not_vat``: code-less lines on VAT accounts that are not VAT (F2431). Both are\nrecorded; both off by default so the common mistake fails loudly.",
      -    "properties": {
      -      "allow_untagged_control": {
      -        "default": false,
      -        "description": "Post an AR/AP control line with no open item (recorded on the entry). Not for VAT-account lines: see not_vat.",
      -        "type": "boolean"
      -      },
      -      "confirm_bank_duplicate": {
      -        "default": false,
      -        "type": "boolean"
      -      },
      -      "not_vat": {
      -        "default": false,
      -        "description": "Acknowledge that code-less lines on VAT accounts (1170/2200...) are not VAT: a reclass within one side, undoing a netting, a payment with a fee line, a payment or settlement on an account used for both directions, or opening balances in a hand-built opening entry (ZET-159). Recorded on the audit row. A VAT payment or settlement on one-direction VAT accounts (only cleared: debit output, credit input; against bank/cash, the settlement account or each other) needs no flag. Off by default: an untagged VAT movement must fail, not miss the MWST-Abrechnung.",
      -        "type": "boolean"
      -      }
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "description": "Optional body for posting a manual entry.\n\n``allow_untagged_control``: an AR/AP control line with no open item (ZET-150).\n``not_vat``: code-less lines on VAT accounts that are not VAT (F2431). Both are\nrecorded; both off by default so the common mistake fails loudly.",
      +    "properties": {
      +      "allow_untagged_control": {
      +        "default": false,
      +        "description": "Post an AR/AP control line with no open item (recorded on the entry). Not for VAT-account lines: see not_vat.",
      +        "type": "boolean"
      +      },
      +      "bank_entry_ids": {
      +        "anyOf": [
      +          {
      +            "items": {
      +              "type": "string"
      +            },
      +            "maxItems": 50,
      +            "type": "array"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "confirm_bank_duplicate": {
      +        "default": false,
      +        "type": "boolean"
      +      },
      +      "confirm_chf_only": {
      +        "default": false,
      +        "type": "boolean"
      +      },
      +      "not_vat": {
      +        "default": false,
      +        "description": "Acknowledge that code-less lines on VAT accounts (1170/2200...) are not VAT: a reclass within one side, undoing a netting, a payment with a fee line, a payment or settlement on an account used for both directions, or opening balances in a hand-built opening entry (ZET-159). Recorded on the audit row. A VAT payment or settlement on one-direction VAT accounts (only cleared: debit output, credit input; against bank/cash, the settlement account or each other) needs no flag. Off by default: an untagged VAT movement must fail, not miss the MWST-Abrechnung.",
      +        "type": "boolean"
      +      },
      +      "suspense_no_movement": {
      +        "default": false,
      +        "type": "boolean"
      +      },
      +      "suspense_no_movement_reason": {
      +        "anyOf": [
      +          {
      +            "maxLength": 500,
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does so well: one-way mutation, 409 refusals from both replace and discard, the permanence of reversals (both rows stay visible), and the single documented in-place exception (PUT …/guessed-account on coding_guessed entries). It omits permission requirements and the shape of the success response, so it is strong but not exhaustive.

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?

Front-loaded with the verb and the 'One-way' warning, then consequences, then the exception, then the imperative closing advice — a logical order with no filler. The em-dash fragment '— accountant. One-way.' is terse but readable in context.

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

Completeness3/5

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

For a destructive, irreversible-by-default mutation with no annotations and no output schema, the description covers consequences and recovery well, which is the highest-risk gap. It is nonetheless incomplete on the input side, leaving the confirmation flags and the body parameter unexplained for an operation where a missed flag causes a hard failure.

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 description coverage is 0% at the top level, and the description never mentions company_id, entry_id, or the optional body at all. Several body fields (confirm_chf_only, bank_entry_ids, suspense_no_movement, confirm_bank_duplicate, suspense_no_movement_reason) are undocumented in both the schema and the description, so an agent gets no guidance on the confirmation flags it likely must set.

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

Purpose4/5

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

States a specific verb and resource ('Post a draft entry into the books') and pins the actor ('accountant'), which lets an agent separate it from create_gl_journal_entry by implication (this consumes a draft, it does not create one). It never names that sibling explicitly, so sibling differentiation rests on inference.

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?

Gives a clear condition ('post a draft entry'), a timing rule ('Check the draft before posting rather than after'), and routes corrections to the '…/reverse' path. It stops short of explicitly naming create_gl_journal_entry or list_gl_journal_entries as the prerequisite/verification tools, so the full workflow is implied rather than spelled out.

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