Skip to main content
Glama
Sign In
@kadam-net/mcp-server

@kadam-net/mcp-server

Official
by kadam-official
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

kadam_adv_list_finance_operations

Read-only

Retrieves financial operations including deposits, charges, and refunds. Use to review account balance, recent transactions, and spending history.

Instructions

Lists financial operations (deposits, charges, refunds). Use to check account balance, recent transactions, and spending history.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kadam_adv_list_finance_operations"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
dateToNoRange end (YYYY-MM-DD); must be paired with dateFrom
perPageNo
dateFromNoRange start (YYYY-MM-DD); must be paired with dateTo
activityTypeNoOperation type filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.3
    • addedInput schema / properties / activityType / description
      Added value: +"Operation type filter"
    • addedInput schema / properties / activityType / enum
      Added value: +[
+  "impression",
+  "deposit",
+  "admin_deposit",
+  "withdrawal",
+  "admin_withdrawal"
+]
    • addedInput schema / properties / dateFrom / description
      Added value: +"Range start (YYYY-MM-DD); must be paired with dateTo"
    • addedInput schema / properties / dateTo / description
      Added value: +"Range end (YYYY-MM-DD); must be paired with dateFrom"
  2. First observedv0.3.9

TDQS

A3.8/5.0
Behavior4/5

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

Annotations include readOnlyHint=true, confirming safety. Description adds purpose and typical use cases. No contradictions, but lacks additional behavioral details like pagination behavior or rate limits. Still, annotations cover the main safety aspect.

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?

Extremely concise: two sentences that front-load the purpose and provide immediate user intent. No wasted words.

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

Completeness3/5

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

No output schema exists, yet description does not mention return format, pagination, or any error conditions. Adequate for basic use but leaves gaps for an AI agent needing full context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 5 parameters with 60% description coverage (page and perPage lack descriptions). The description does not add any parameter-specific meaning beyond what is in the schema, failing to compensate for the gaps.

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?

Clearly specifies the verb 'Lists' and resource 'financial operations', with examples (deposits, charges, refunds) and intended use (check account balance, transactions). This distinguishes it from sibling tools like list_campaigns or list_audiences.

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?

Provides context for usage ('check account balance, recent transactions, and spending history') but does not explicitly state when not to use or mention alternatives among siblings. The guidance is implicit rather than explicit.

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