Skip to main content
Glama
Sign In
Agentic AQUA

Agentic AQUA

Official
by AquaWallet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pix_list

List PIX→DePix deposits from Ankara’s authoritative database and refresh their local cache entries, with optional status, date range, and deposit ID filters.

Instructions

List PIX → DePix deposits from Ankara's authoritative database and refresh their local cache entries. All filters are optional and combined. To answer requests such as 'today' or 'last week', convert the requested period to inclusive UTC dates in YYYY-MM-DD format and pass date_from/date_to.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "<email>"
    },
    "name": "pix_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesJAN3 account email that owns the deposits
statusNoReturn only deposits with this status
date_toNoInclude deposits created on or before this UTC date
date_fromNoInclude deposits created on or after this UTC date
deposit_idNoReturn only this Ankara deposit id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a real side effect – refreshing local cache entries during a read – which is valuable. But it says nothing about authentication/ownership requirements (the required email), pagination or result limits, or what happens when the cache refresh fails, leaving key behavior undisclosed for an unannotated tool.

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 tight sentences, front-loaded with the action, then the filter semantics and date-conversion tip. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Five parameters, no output schema and no annotations, yet the description never describes what a deposit record returns (id, status, amounts, timestamps) or how many results to expect. For an unannotated list tool with no output schema, this leaves the agent under-informed about the response.

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 per-parameter descriptions and a status enum, so the baseline is 3. The description adds the date-range convention (inclusive UTC, YYYY-MM-DD) and notes filters compose, which is marginally beyond the schema but mostly restates the parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: lists PIX→DePix deposits and refreshes local cache entries. The scope ('Ankara's authoritative database') and the cache-refresh side effect make it distinguishable from pix_status/pix_receive, though it never names those siblings explicitly.

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?

Gives useful guidance that all filters are optional and combined, plus an instruction to convert relative periods like 'today' or 'last week' into inclusive UTC dates. It does not say when to reach for this tool versus pix_status, nor what to do when a requested deposit is not found.

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