Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaRelated ServersScoreDiscussions(1)
Rust
Hybrid

Statement List

statement_list
Read-onlyIdempotent

List available daily or monthly account statements by date range. Get statement IDs to export and download them.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
listYes

Schema Changelog

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

  1. 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."
  2. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"StatementListParam"
  3. 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"
  4. 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"
+}
  5. Addedv0.4.5
  6. Removedv0.4.0
  7. Addedv0.3.2
  8. Removedv0.3.1
  9. First observedv0.1.12

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context that returned ids are intended for use with statement_export. However, it does not disclose additional behavioral traits such as pagination, ordering, or how 'available' is determined, though the output schema and parameter descriptions supply some of this.

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 two short sentences with no filler. The core purpose is front-loaded, and the workflow hint about using the id with statement_export is placed second. Every sentence earns its place.

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

Completeness5/5

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

For a read-only listing tool with three optional, well-documented parameters and an output schema present, the description is sufficient. It explains the resource, the statement frequency options, and how to connect to the download tool. The annotations and schema carry the remaining operational details, so nothing critical is missing.

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 description coverage is 100%, and the schema already provides detailed descriptions for all three parameters including defaults for limit and start_date based on statement_type. The tool description only repeats the daily/monthly distinction already present in the statement_type parameter description, adding no meaningful semantics beyond 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 states a specific verb and resource: 'List available account statements (daily/monthly).' It clearly identifies the tool's scope and distinguishes it from the related statement_export tool by explaining that the ids from this listing are used for download. An agent can immediately understand what this tool does.

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

Usage Guidelines5/5

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

The description explicitly directs the agent to use statement_export with the id to download statements, clarifying the complementary relationship and when to use each tool. It tells the agent what to do with the output of statement_list, making the workflow explicit. No further alternative-selection guidance is needed for this simple listing tool.

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/longbridge/longbridge-mcp'

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