Skip to main content
Glama
anhermon

spark-ordernet-mcp

by anhermon

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ORDERNET_BROKERYesBroker slug: one of meitav, psagot, ibi, nesua, gaon
ORDERNET_PASSWORDYesYour brokerage password
ORDERNET_USERNAMEYesYour brokerage username

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
accountsA

List the brokerage accounts this login can read.

portfolioB

Current holdings, cash and totals for an account — the snapshot to analyse.

Returns positions (quantity, cost, market value, % of portfolio, last price), the account summary (value, cash, credit, withdrawable) and securities totals.

transactionsB

Account transaction history between two dates (YYYY-MM-DD).

Buys, sells, dividends, fees, deposits and withdrawals. The API returns garbage when a range spans calendar years, so ranges are split per year automatically. Set dollar=True for the foreign-currency ledger.

ordersC

Orders for a given day (YYYY-MM-DD, default today): status, fills, prices.

order_historyC

Execution and status history for one order returned by orders().

standing_ordersB

Standing-order definitions visible to the authenticated login.

yieldsC

Account return/value series for a year, monthly-style or daily-style.

Monthly fields include NominalYield, RealYield, DollarYield, Value, and MONTH_DEPOSITE_WITHRWALS. Daily-style fields include Date, NominalYield, TheoreticalYield, Value, and Deposite.

search_securitiesA

Find a security by symbol, name or TASE number. Returns topic keys usable with price_history. The platform has no search endpoint — this searches the public static instrument universe the SPA itself searches client-side. Results contain only allowlisted public security metadata.

resolve_securitiesA

Resolve exact public security identifiers to safe display metadata.

The static universe is scanned once. Account-shaped topics and raw static rows are never returned. Ambiguous identifiers remain unresolved.

price_historyA

Daily OHLCV history for a security. topic_key looks like RZF_0000001 (TASE), KRN_0000002 (fund) or CLPS_999_EXMPL (foreign) — get it from resolve_securities, search_securities, or a position key from portfolio().

latest_newsC

Latest market-news items available in Spark.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 11 tools

Disambiguation5/5

Each tool targets a distinct aspect: orders vs history, securities search vs resolution, accounts vs portfolio vs transactions. No two tools overlap in purpose.

Naming Consistency3/5

Names mix plural nouns (orders, yields, accounts, portfolio) with verb_noun (search_securities, resolve_securities) and noun_noun patterns (price_history, order_history, standing_orders, latest_news). No single consistent convention.

Tool Count5/5

11 tools cover a reasonable scope for a brokerage MCP: orders, history, positions, securities lookup, price data, news, accounts, and transactions. Not too few or too many.

Completeness3/5

Covers read operations well but lacks write tools like place_order, modify_standing_order, or cancel. Missing create/update/delete for orders and accounts, limiting full lifecycle coverage.

Maintenance

ActivitySlowing
ResponsivenessNo issues