Skip to main content
Glama
Frihet-io

Frihet MCP Server

by Frihet-io

List Deposits

list_deposits
Read-onlyIdempotent

List deposits filtered by date range, status, or client ID with pagination. Returns deposits sorted by date (newest first).

Instructions

List all deposits with optional pagination and date range filters. Returns deposits sorted by date (newest first). Example: from='2026-01-01', to='2026-03-31', clientId='abc', limit=50 / Lista todos los depositos con paginacion y filtros de fecha opcionales.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd date filter (YYYY-MM-DD) / Fecha fin
fromNoStart date filter (YYYY-MM-DD) / Fecha inicio
afterNoCursor for cursor-based pagination (document ID) / Cursor para paginacion basada en cursor
limitNoMax results (1-100) / Resultados maximos
fieldsNoComma-separated field names to return (e.g. 'id,amount,status') / Campos a devolver
offsetNoOffset / Desplazamiento
statusNoFilter by status (e.g. 'pending', 'applied', 'refunded') / Filtrar por estado
clientIdNoFilter by client ID / Filtrar por ID de cliente

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
limitYes
totalYes
offsetYes
nextCursorNo
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds sorting order (newest first) and pagination methods (cursor/offset), going beyond annotations.

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?

Two sentences with an example, front-loaded. Bilingual text adds length but is acceptable. No extraneous information.

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 output schema present, return values are covered. Description covers purpose, pagination, sorting, and filters. Adequate for an 8-parameter list tool.

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% with good descriptions for all parameters. The description adds an example but no new semantic meaning beyond what the schema provides.

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 all deposits" with verb and resource, specifies sorting order (newest first), and distinguishes from sibling tools like get_deposit or create_deposit.

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?

Provides example usage and mentions optional pagination/date filters, but does not explicitly compare to sibling tools. However, as the only list tool for deposits, context is clear.

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/Frihet-io/frihet-mcp'

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