Skip to main content
Glama
Sign In
NitroStack Calculator MCP Server

NitroStack Calculator MCP Server

by Tarika06
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

classify_transaction_batch

Classify a batch of raw transactions by assigning merchant category, EMI/recurring-bill/salary flags, and a confidence score.

Instructions

Classifies a batch of raw transactions into merchant category, EMI/recurring-bill/salary flags, and confidence score.

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": {
      "transactions": "<transactions>"
    },
    "name": "classify_transaction_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
transactionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only mentions output types. It omits behavioral traits like determinism, error handling, rate limits, or confidence score interpretation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (one sentence) and front-loaded, but overly brief given the tool's complexity. It sacrifices necessary detail for brevity.

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?

The tool has one input parameter and no output schema. The description does not detail possible categories, flags, confidence score range, or output structure, leaving the agent underinformed.

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 coverage is 0%, and the description does not explain the transactions parameter structure, meaning of fields, or expected format beyond what the schema already shows.

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 states it classifies raw transactions into merchant category, EMI/recurring-bill/salary flags, and confidence score. This is specific and distinguishes it from sibling tools like fetch_transaction_stream and ingest_financial_document.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. It only states the function without context.

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