Skip to main content
Glama
iseppo

e-arveldaja MCP Server

by iseppo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Journals

list_journals
Read-onlyIdempotent

Retrieve paginated journal entries, optionally filtered by date, client, registration status, operation type, or document number; use brief or full views to inspect headers.

Instructions

List journal entries. Paginated. Brief view omits postings; use view='full' for headers or get_journal for postings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default 1)
viewNoResponse detail: brief (default) returns triage fields; full returns every API field.
date_toNoOnly journals with effective_date <= this (YYYY-MM-DD). Filters by effective_date; narrowed server-side.
per_pageNoItems per page when filtering (default 100, max 500)
date_fromNoOnly journals with effective_date >= this (YYYY-MM-DD). Filters by effective_date; narrowed server-side.
clients_idNoFilter by clients_id
registeredNoOnly registered (true) or unregistered (false) journals
modified_sinceNoReturn only objects modified since this timestamp (ISO 8601)
operation_typeNoFilter by operation_type (e.g. INITIAL for UI-managed opening balances, ENTRY, TRANSACTION, SALE_INVOICE, PURCHASE_INVOICE)
document_number_containsNoCase-insensitive substring match on document_number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.32.1
    • changedInput schema / properties / operation_type / description
      Previous value: -"Filter by operation_type (e.g. ENTRY, TRANSACTION, SALE_INVOICE, PURCHASE_INVOICE)"New value: +"Filter by operation_type (e.g. INITIAL for UI-managed opening balances, ENTRY, TRANSACTION, SALE_INVOICE, PURCHASE_INVOICE)"
  2. Changed1 schema field changedv0.29.2
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observedv0.18.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds useful behavioral context beyond annotations: results are paginated, brief view omits postings, and full view returns headers.

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?

Three short sentences, front-loaded with the core action. Every sentence earns its place by covering listing, pagination, and the view/get_journal tradeoff.

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?

Given rich schema coverage and safety annotations, the description is nearly complete for a list tool. It covers pagination and the main view distinction, though without an output schema it could say slightly more about return shape.

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 100%, so the baseline is 3. The description adds meaningful clarification about the view parameter: brief omits postings, while full is for headers, which supplements the schema's brief/full distinction.

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: "List journal entries." It further distinguishes the tool from get_journal by explaining that brief view omits postings and directing postings retrieval to get_journal.

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 explicit guidance for the main decision point: use view='full' for headers, or get_journal for postings. It does not state broader when-not-to-use conditions, but the key alternative is named with its condition.

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