Skip to main content
Glama
steamau

Beeswax Shares MCP Server

by steamau

Create holding

create_holding

Register a new security holding in a fund for a first-time purchase. For existing holdings, use record_trade.

Instructions

Create a brand-new holding (security/asset) in the fund — use ONLY when a security was purchased that the fund has never held before (check list_holdings first). For buys of an existing holding, use record_trade instead. Note: unlike the record_* tools, this writes the holding directly; the buy transaction itself should still go through record_trade for human review.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSecurity name, e.g. "Vanguard Australian Shares Index ETF"
notesNo
fund_idYesFund ID (discover via whoami or list_funds)
currencyNoCurrency code (default "AUD")
exchangeNoExchange, e.g. "ASX"
quantityNoUnits acquired
broker_idNoBroker ID (see list_brokers)
asset_typeNoAsset type by name or category string, e.g. "ETF" or "equity" (see list_asset_types). Defaults to equity.
ticker_symbolNoTicker, e.g. "VAS"
acquisition_dateNoAcquisition date as an ISO date, e.g. "2026-05-30"
purchase_price_per_unitNoPurchase price per unit in AUD
Behavior5/5

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

Annotations indicate a non-destructive write; the description adds that this writes the holding directly while the buy transaction should still go through record_trade for review, providing full context beyond annotations.

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?

Two sentences plus a note, front-loaded with purpose and usage, no wasted words.

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?

Covers purpose, usage, behavioral notes, and workflow integration. Missing explicit mention of return value, but given standard creation tools, this is acceptable.

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 coverage is 91% with good descriptions for each parameter; the description adds minimal new semantics but reinforces usage context. Baseline 3 is appropriate.

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 the tool creates a new holding (security/asset) under the specific condition of a previously unheld security, distinguishing it from sibling tools like record_trade.

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

Usage Guidelines5/5

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

Explicitly tells when to use (only for never-before-held securities) and provides an alternative tool (record_trade) for existing holdings, along with a prerequisite to check list_holdings first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/steamau/beeswax-desktop'

If you have feedback or need assistance with the MCP directory API, please join our Discord server