Skip to main content
Glama

Show XMemo expenses

list_ledger_transactions
Read-onlyIdempotent

Search past expenses and purchases in your personal ledger. Filter by date, category, amount, or transaction type to answer finance questions.

Instructions

Show XMemo Ledger records. Call this when the user asks about past expenses, purchases, or spending history, or before answering a finance question that depends on recorded transactions. For item searches use query and leave currency blank unless a currency was requested.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return.
queryNoNatural-language question or search text.
scopeNoOptional scope that narrows memory access; leave blank for the token default.
bucketNoMemory bucket or namespace to read from or write to; use % only for tools that support wildcard reads.%
offsetNoNumber of matching records to skip for pagination.
date_toNoOnly include ledger transactions on or before this YYYY-MM-DD date.
categoryNoOptional spending category, such as food, transport, or electronics.
currencyNoCurrency code or label, such as CNY, RMB, JPY, yen, or USD. For ledger search/list tools, leave blank unless the user explicitly requested one currency; labels are normalized to codes.
date_fromNoOnly include ledger transactions on or after this YYYY-MM-DD date.
max_amountNoOnly include ledger transactions with amount less than or equal to this value.
min_amountNoOnly include ledger transactions with amount greater than or equal to this value.
output_jsonNoReturn a machine-readable JSON response instead of a human-readable summary.
transaction_typeNoOptional ledger type filter: expense, income, refund, or transfer.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already provide readOnlyHint=true and destructiveHint=false. The description adds behavioral nuance about leaving currency blank for most cases, which is useful but not extensive. No contradiction.

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?

Two sentences, front-loaded with purpose, no wasted words. Every sentence adds value.

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 13 parameters, zero required, and an output schema, the description covers core use and key parameter hints. Could mention pagination or return format, but overall adequate.

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 baseline is 3. The description adds extra guidance on the 'query' and 'currency' parameters beyond the schema, improving parameter semantics.

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 'Show XMemo Ledger records' with a specific verb and resource, and distinguishes from sibling tools like add_expense (create) and get_monthly_ledger_summary (summary) by focusing on listing past transactions.

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 tells when to call ('when the user asks about past expenses, purchases, or spending history, or before answering a finance question') and provides a key usage hint ('For item searches use query and leave currency blank unless a currency was requested').

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/yonro/memory-os-cli'

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