Skip to main content
Glama
longbridge

longbridge

Official

Statement List

statement_list
Read-onlyIdempotent

List available daily or monthly account statements to retrieve their IDs for downloading through the export tool.

Instructions

List available account statements (daily/monthly). Use the id with statement_export to download.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_jqNoOptional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response.
limitNoNumber of records to return. Defaults to 30 for "daily" or 12 for "monthly". The default depends on `statement_type`, so the schema declares none: `skip_serializing_if` is what stops schemars deriving `default: null` from `serde(default)`, which would contradict the integer type.
start_dateNoStart date (yyyy-mm-dd). Defaults to 30 days ago for "daily" or 12 months ago for "monthly".
statement_typeNoStatement type: "daily" (default) or "monthly".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.0
    • addedInput schema / properties / _jq / description
      Added value: +"Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response."
    • removedInput schema / properties / limit / format
      Removed value: -"int32"
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -{
      -  "$defs": {
      -    "StatementItem": {
      -      "properties": {
      -        "dt": {
      -          "format": "int32",
      -          "type": "integer"
      -        },
      -        "file_key": {
      -          "type": "string"
      -        }
      -      },
      -      "required": [
      -        "dt",
      -        "file_key"
      -      ],
      -      "type": "object"
      -    }
      -  },
      -  "properties": {
      -    "list": {
      -      "items": {
      -        "$ref": "#/$defs/StatementItem"
      -      },
      -      "type": "array"
      -    }
      -  },
      -  "required": [
      -    "list"
      -  ],
      -  "type": "object"
      -}New value: +null
  3. Changed2 schema fields changedv0.10.0
    • removedInput schema / properties / limit / default
      Removed value: -null
    • changedInput schema / properties / limit / description
      Previous value: -"Number of records to return. Defaults to 30 for \"daily\" or 12 for \"monthly\"."New value: +"Number of records to return. Defaults to 30 for \"daily\" or 12 for \"monthly\".\n\nThe default depends on `statement_type`, so the schema declares none:\n`skip_serializing_if` is what stops schemars deriving `default: null`\nfrom `serde(default)`, which would contradict the integer type."
  4. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"StatementListParam"
  5. Changed6 schema fields changedv0.6.0
    • removedOutput schema / $defs / StatementItem / properties / dt / description
      Removed value: -"Statement date as a `yyyymmdd` integer (e.g. `20240115`)."
    • removedOutput schema / $defs / StatementItem / properties / file_key / description
      Removed value: -"Opaque file key identifying this statement. Pass to `statement_export`\nto obtain a pre-signed download URL."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `statement_list`.\n\nWraps a `list` array of statement entries. The SDK's `StatementItem`\n(`{ dt: i32, file_key: String }`) is emitted unchanged by the transform\npipeline: `dt` is a plain integer date (`yyyymmdd`, e.g. `20240115`) that is\nnot a `*_at` field and so is left as a number, and `file_key` does not match\nthe counter_id pattern."
    • removedOutput schema / properties / list / description
      Removed value: -"Available statements in the requested range."
    • removedOutput schema / title
      Removed value: -"StatementListResponse"
  6. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "StatementItem": {
      +      "properties": {
      +        "dt": {
      +          "description": "Statement date as a `yyyymmdd` integer (e.g. `20240115`).",
      +          "format": "int32",
      +          "type": "integer"
      +        },
      +        "file_key": {
      +          "description": "Opaque file key identifying this statement. Pass to `statement_export`\nto obtain a pre-signed download URL.",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "dt",
      +        "file_key"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "description": "Returned by `statement_list`.\n\nWraps a `list` array of statement entries. The SDK's `StatementItem`\n(`{ dt: i32, file_key: String }`) is emitted unchanged by the transform\npipeline: `dt` is a plain integer date (`yyyymmdd`, e.g. `20240115`) that is\nnot a `*_at` field and so is left as a number, and `file_key` does not match\nthe counter_id pattern.",
      +  "properties": {
      +    "list": {
      +      "description": "Available statements in the requested range.",
      +      "items": {
      +        "$ref": "#/$defs/StatementItem"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "list"
      +  ],
      +  "title": "StatementListResponse",
      +  "type": "object"
      +}
  7. Addedv0.4.5
  8. Removedv0.4.0
  9. Addedv0.3.2
  10. Removedv0.3.1
  11. First observedv0.1.12

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds useful behavior beyond that: the returned records expose an id intended for statement_export, and the list is restricted to daily/monthly statements. It doesn't describe pagination or return format, but that is less critical given the 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 a single efficient sentence with no filler. It front-loads the core purpose and immediately adds the actionable cross-tool instruction, earning every word.

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?

For a simple read-only list tool with fully documented parameters, the description is nearly sufficient. It names the companion tool and the id contract, though it doesn't describe the response fields beyond implying an id. With no output schema present, a bit more detail about what fields are returned could be helpful, but the current text covers the essential workflow.

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?

The input schema covers all parameters with descriptions, including statement_type, limit, start_date, and _jq. The description's mention of 'daily/monthly' aligns with statement_type but adds no deeper semantic detail beyond what the schema already provides, so the baseline of 3 is appropriate.

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 identifies the action ('List available account statements'), the resource ('account statements'), and the key dimension (daily/monthly). It also distinguishes this tool from statement_export by stating the id is meant for that export flow, so an agent can tell them apart.

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 gives clear context: use this to list statements, then use the id with statement_export to download. It doesn't explicitly say when not to use this tool or name alternative listing tools, but the workflow relationship to statement_export is a strong practical guideline.

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