Skip to main content
Glama
Sign In
monacloud-mcp

monacloud-mcp

Official
by mona-software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Tra giao dịch tiền vào

monapay_list_transactions
Read-onlyIdempotent

List incoming transactions by virtual account, with pagination up to 100 per page, to support payment reconciliation.

Instructions

Liệt kê giao dịch tiền vào theo tài khoản ảo, phân trang tối đa 100/trang; dùng để đối soát. / List incoming transactions.

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": {
      "virtual_account_number": "<virtual_account_number>"
    },
    "name": "monapay_list_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
virtual_account_numberYesSố tài khoản ảo (bắt buộc; lấy từ monapay_list_virtual_accounts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the pagination cap ('tối đa 100/trang'), which is useful behavioral context, but says nothing about return shape or ordering.

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?

A short two-clause sentence with the resource and scope front-loaded; the bilingual duplication is slightly redundant but harmless. Every clause carries 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?

For a read-only list tool with full safety annotations and no output schema, the description covers resource, scope, and pagination. The only gap is the absence of any detail on what a transaction record contains, which is minor given there is no output schema to anchor it.

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 only 33% (only virtual_account_number is documented, pointing to monapay_list_virtual_accounts). The description reinforces the limit ceiling ('tối đa 100/trang') but leaves 'page' semantics and ordering unexplained, so it only partially compensates for the low coverage.

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?

The description states a specific verb+resource: 'Liệt kê giao dịch tiền vào' (list incoming transactions) scoped 'theo tài khoản ảo' (by virtual account). This clearly separates it from sibling list tools like monapay_list_checkouts or monapay_list_virtual_accounts, though it never names an alternative to distinguish against.

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?

'dùng để đối soát' (used for reconciliation) implies the intended use case, which is genuine context. However, it gives no when-not conditions, no prerequisites, and no explicit alternatives among the many monapay list siblings.

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