Skip to main content
Glama
zenskar

Zenskar MCP Server

Official
by zenskar
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

createJournalEntry

createJournalEntry

Record accounting transactions by creating a manual journal entry with debit and credit lines.

Instructions

Create a new manual journal entry with debit and credit lines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
posted_atNoPosting date of the journal entry in ISO 8601 format (e.g., '2026-01-15T00:00:00').
descriptionYesDescription/memo for the journal entry.
currencyYesThree-letter ISO 4217 currency code (e.g., 'USD', 'EUR', 'GBP').
journal_linesYesArray of journal lines. Each line requires: {account_id, debits, credits, currency}. Use 'debits' and 'credits' (plural, integers in cents). Example: [{account_id:'...', debits:10000, credits:0, currency:'USD'}, {account_id:'...', debits:0, credits:10000, currency:'USD'}]. Optional tags: customer_id, contract_id, invoice_id, custom_tags.
custom_dataNoAdditional metadata as key-value pairs.
status_typeNoJournal entry status (default: 'posted').posted
__userContextNoInternal user context for multi-tenant authentication and approval workflow

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only states 'Create' but does not disclose authorization needs, validation, defaults (e.g., status_type='posted'), or side effects.

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

Conciseness5/5

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

One concise sentence with no redundancy, front-loads the key action and resource.

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?

Despite complex nested parameters and accounting concepts, the description is minimal. It does not explain debit/credit semantics, output, or the role of __userContext.

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

Parameters3/5

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

Schema description coverage is 100% with detailed parameter descriptions. The tool description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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?

The description clearly states the tool creates a new manual journal entry with debit and credit lines, which is specific and distinguishes it from sibling tools like listJournalEntries.

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?

No guidance on when to use this tool versus alternatives, no prerequisites or when-not-to-use mentioned. The description lacks context for optimal invocation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zenskar/mcp-zenskar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server