Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Fee rates

account_fees
Read-onlyIdempotent

Retrieve your account's buy and sell fee rates and order-preview formulas, including broker, exchange, levy, VAT, and income-tax components.

Instructions

The account's buy and sell fee rates (broker, exchange, levy, VAT, income tax components) and the formulas the app uses to preview an order.

Needs the trading session (stockbit-mcp login --trading). Values IDR; lots of 100 shares.

Returns (Stockbit's data field): {message, data:{version, formula:{buy:{invested,invested_fee,fee,broker_fee,exchange_fee}, sell:{...}, ca_sell:{...}, sell_profit_loss, sell_gain, day_trade:{portion_order_amount,debt:{unrealized,ratio},investment:{day_trade,portion_tb}}, amount_invested, unrealized:{...}, summary:{...}, margin_trading:{...}, margin_stock_transfer:{...}, margin_cash_transfer:{...}} (all strings = arithmetic expressions over LOT, PRICE, FEE_BUY, FEE_SELL, BROKER_FEE, EXCHANGE_FEE_TOTAL_BUY/SELL...), fee:{buy,sell} (fractions), preview_fee:{broker_fee, exchange:{title,desc,subtitle,compositions:[{name,value,type}],total_title,total_buy,total_sell,total_ca_buy,total_ca_sell}}, day_trade:{fee:{buy,sell}, portion…

Endpoint: GET carina /formula/v2.

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": "account_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description goes further by disclosing the auth/session requirement, that values are in IDR and quoted in lots of 100 shares, and the concrete endpoint (GET carina /formula/v2). That is genuine context beyond the structured fields. The return section is present but garbled/truncated, which weakens it slightly.

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 opening two sentences are tight and front-loaded, and the auth/units sentence earns its place. However, the return-value section is a very long nested blob that truncates mid-token ('portion…'), leaves unbalanced braces, and reads like a raw payload dump rather than a usable summary — noise that an agent cannot reliably parse.

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?

With no output schema, the description carries the burden of explaining returns and does attempt it, along with auth, currency, unit conventions and the endpoint. But the response description is only partially legible and the formula-expression semantics (over LOT, PRICE, FEE_*) are only sketchily conveyed. Adequate, not complete, for a zero-param tool whose whole value is the returned structure.

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

Parameters4/5

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

The tool takes zero parameters and the description correctly spends no words on inputs, so the baseline of 4 applies. No parameter meaning is missing because there are none.

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?

States a specific resource and scope: 'the account's buy and sell fee rates' with the component breakdown (broker, exchange, levy, VAT, income tax) plus the preview formulas. An agent knows exactly what it retrieves. It does not name or contrast any sibling such as account_trading_info, so it stops short of a 5.

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?

Usage is only implied via 'the formulas the app uses to preview an order' — no explicit when-to-use, when-not-to-use, or alternative named. It does supply a real prerequisite ('Needs the trading session (stockbit-mcp login --trading)'), which is valuable, but that is a precondition rather than guidance on tool selection.

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