Skip to main content
Glama
IsidoreSoftware

Ogarni.AI MCP Server

by IsidoreSoftware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Purchase Documents

ogarniai_list_documents
Read-onlyIdempotent

List receipts and invoices filtered by date range with sorting, returning store name, total, items, categories, and tags for personal finance tracking.

Instructions

List receipts and purchase documents with optional date filters and sorting.

Returns a paginated list of purchase documents (receipts, invoices, email purchases) with store name, total amount, items, categories, and tags.

Args:

  • from (string, optional): Start date filter (ISO 8601, e.g. "2024-01-01")

  • to (string, optional): End date filter (ISO 8601, e.g. "2024-12-31")

  • sortBy (string, optional): Sort field - "purchase_time" (default) or "created_at"

  • sortDirection (string, optional): Sort order - "desc" (default) or "asc"

Returns: JSON array of purchase documents with fields: id, storeName, purchaseTime, totalAmount, currency, items[], tags[], groupId, hasDuplicates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd date filter (ISO 8601 format, e.g. 2024-12-31)
fromNoStart date filter (ISO 8601 format, e.g. 2024-01-01)
sortByNoField to sort bypurchase_time
sortDirectionNoSort directiondesc

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already mark the operation as read-only and idempotent, and the description adds behavioral detail by stating the result is paginated, is a JSON array, and includes a concrete field list. It also clarifies which document subtypes are included, going beyond what the annotations alone provide.

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 description is well-structured with a summary line, an Args list, and a Returns field list, with no filler. There is minor redundancy around 'receipts' and purchase documents, but the overall length is appropriate and front-loaded.

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?

With no output schema, the description compensates by enumerating the exact return fields and documenting all four optional parameters. It would be slightly richer if 'categories' appeared in the return field list, but the tool can still be invoked and interpreted confidently.

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%, and the Args section largely mirrors the schema. It adds ISO 8601 date examples and restates defaults for sortBy and sortDirection, but these are already present in the schema, so the description does not add substantial meaning beyond the structured input definitions.

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 opens with a clear action verb and resource: 'List receipts and purchase documents' with optional date filters and sorting. The returned paginated list and document subtypes make the tool's scope unambiguous and distinguish it from single-document siblings like ogarniai_get_document.

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?

The description clearly frames this as the tool to use when a paginated list of purchase documents is needed, with date and sorting controls. It does not explicitly name alternatives, but the list-vs-single distinction is clear from both the description and the sibling tool names.

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