Skip to main content
Glama

increase

by io.usefulapi

List transactions

increase_list_transactions
Read-only

List settled transactions. Increase API: GET /transactions. Filter by account, category (sent as category.in), and created date range (created_at.after / created_at.before).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size, 1–100. Default 100.
cursorNoOpaque pagination cursor from a previous response's next_cursor.
categoryNoTransaction category filter (sent as category.in).
account_idNoOnly transactions for this account id.
created_afterNoISO 8601 timestamp; only transactions created at/after this (sent as created_at.after).
created_beforeNoISO 8601 timestamp; only transactions created before this (sent as created_at.before).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already provide readOnlyHint: true, indicating no side effects. The description adds that the tool lists settled transactions and supports filtering, but does not disclose additional behavioral traits such as pagination behavior or rate limits. It does not contradict annotations.

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?

The description is extremely concise: two sentences covering purpose and key details. It is front-loaded with the core function and avoids unnecessary words.

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 the tool has 6 parameters and no output schema, the description provides a good overview of filtering capabilities but does not mention pagination (cursor, limit) or the return format. However, the title and parameter descriptions compensate somewhat.

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 the input schema already documents each parameter. The description summarizes filtering options but does not add new semantics beyond what is already in the schema. Baseline 3 applies.

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 'List settled transactions', which provides a specific verb and resource. It distinguishes from sibling tools like 'increase_list_pending_transactions' and 'increase_list_declined_transactions' by specifying that only settled transactions are returned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus alternatives like list_pending_transactions or get_transaction. Usage is implied by the term 'settled', but no direct guidance or exclusions are provided.

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

All increase toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation5/5

Each tool targets a distinct resource type (account, account number, ACH transfer, etc.) with clear verb_noun naming, making them easily distinguishable.

Naming Consistency5/5

All tools follow a consistent `increase_verb_noun` pattern in snake_case, with verbs like create, get, list, lookup.

Tool Count4/5

18 tools is slightly above the typical 3-15 range, but the scope of banking operations (accounts, transfers, transactions, cards, entities) justifies the count.

Completeness2/5

The server is heavily read-only with only one mutation (create_external_account). Missing create/update/delete for accounts, transfers, cards, etc., which limits its usefulness for full banking workflows.

Resources