Skip to main content
Glama
Sign In
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Snapshot 30 June valuations for listed holdings

snapshot_eofy_valuations

Prices listed fund holdings at a financial year's 30 June using Yahoo closes, flags stale evidence, skips unlisted assets, and protects evidence-backed or locked valuations. Safe to re-run.

Instructions

Price every LISTED holding the fund held at a financial year's 30 June from the Yahoo Finance close on or before that date, and record it as the year's valuation (source yahoo) with evidence naming the symbol, trade date and fetch date (flagged STALE when the last trade is more than 5 trading days earlier). Unlisted trusts, private equity, property and other unlisted assets are left unvalued, so gap G3 stays open for them until record_valuation is called with real evidence. Never overwrites a valuation that has evidence or source statement, and never a locked year. Safe to re-run. Returns result counts (priced, failed, stale, skipped_unlisted, skipped_protected, skipped_locked) and the year's valuations as list_valuations does.

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": {
      "fund_id": "<fund_id>",
      "financial_year": "<financial_year>"
    },
    "name": "snapshot_eofy_valuations"
  }
}

Input Schema

NameRequiredDescriptionDefault
fund_idYesFund ID (discover via whoami or list_funds)
reasoningNoWhy you are making this change — recorded on the audit log entry for this write
external_refNoYour stable ID for this write (e.g. a statement line or document reference). Repeating a call with the same external_ref replays the first result instead of writing twice.
financial_yearYesFinancial year — the label "2023-24" or its numeric id (from list_financial_years)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.8.1

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the write-guard rules, the STALE threshold (more than 5 trading days since last trade), which holdings are skipped and why, and idempotent re-run behavior. It even enumerates the result counters returned, so the agent knows what a partial run looks like.

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

Conciseness4/5

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

Front-loads the action and pricing rule, then layers in protections, alternatives, and return shape in a logical order. The sentences are dense and long, but each carries distinct operational information rather than restating the name.

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

Completeness5/5

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

For a write tool with no output schema, the description covers the source, the dating rule, the skip and protection semantics, the alternative path for unlisted assets, and the shape of the response. An agent has everything needed to invoke it correctly and interpret a partial result.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by making clear that financial_year selects the 30 June pricing date and the year label the valuation is recorded against. It does not add syntax or format detail for fund_id or reasoning beyond what the schema already states.

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?

Names a specific verb (price/record), a specific resource (listed holdings at 30 June), and a specific data source (Yahoo Finance close on or before that date). It is clearly distinguishable from siblings such as record_valuation, update_price, and list_valuations.

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 states when this tool does not apply (unlisted trusts, private equity, property) and routes the agent to the alternative, record_valuation with real evidence. It also states the protection conditions (never overwrite an evidenced valuation or a locked year) and that re-running is safe, which removes ambiguity about when to call it.

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