Skip to main content
Glama
nikan

elorus-mcp

by nikan

list_expenses

Retrieve expense records with pagination. Filter by supplier, expense category, or date range to find specific expenses.

Instructions

List expense records. Returns paginated results. Filter by supplier, category, or date range.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default: 1)
searchNoSearch term for expense description or supplier name
orderingNoSort field, e.g. '-date' for newest first
supplierNoFilter by supplier contact ID
page_sizeNoResults per page (default: 20, max: 100)
date_afterNoFilter expenses on or after this date (YYYY-MM-DD)
date_beforeNoFilter expenses on or before this date (YYYY-MM-DD)
expense_categoryNoFilter by expense category ID (obtain from list_expense_categories)
Behavior3/5

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

With no annotations, the description must convey behavior. It states 'Returns paginated results' but does not explicitly confirm read-only or mention auth/rate limits. It is adequate but lacks full transparency.

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 concise sentences with key info front-loaded. No redundancy.

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?

The description covers pagination and filter options. No output schema, but the tool is straightforward. Could mention default ordering or that results are read-only, but still complete enough.

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 coverage is 100%, so baseline is 3. The description summarizes filters but does not add new semantics beyond the schema parameter descriptions.

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 verb 'list' and resource 'expense records', and includes pagination and filtering options. It distinguishes from sibling tools like list_bills and list_invoices by specifying 'supplier, category, or date range' filters.

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 implies when to use the tool (listing expenses with filters) but does not explicitly mention when not to use alternatives like get_expense for single records or create_expense for adding.

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/nikan/elorus-mcp'

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