Skip to main content
Glama
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau

Get a historical market close

get_historical_price
Read-only

Retrieve the end-of-day closing price for a listed ticker on a given date, falling back to the last trading day if the market was closed; not for unlisted assets.

Instructions

Look up the Yahoo Finance end-of-day close for a LISTED ticker on a date — the close on that day, or the last trading day before it if it didn't trade (weekend, holiday, suspension). Records nothing. Returns symbol (e.g. MDX.AX), trade_date, close, currency, trading_days_before_requested, stale (true when the last trade is more than 5 trading days before the date — check for a suspension or delisting) and the evidence line to pass to record_valuation. Not for unlisted trusts, private equity or property: those have no market price and need a statement or valuer's report.

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": {
      "ticker": "<ticker>",
      "date": "<date>"
    },
    "name": "get_historical_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate to price as an ISO date, e.g. "2026-05-30"
tickerYesTicker without exchange suffix, e.g. "MDX" or "BHP"
currencyNoConvert the close into this currency, e.g. "AUD"
exchangeNoExchange (default ASX)

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?

Annotations only declare readOnlyHint=true, and the description reinforces it with 'Records nothing' while adding genuinely new behavior: the last-trading-day fallback for weekends, holidays and suspensions, and the stale flag semantics (>5 trading days implies possible suspension or delisting). It also enumerates the returned fields, which matters since there is no output schema.

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-loaded with the core action, then scope exclusions, with no filler sentences. Slightly dense due to nested parentheses around the fallback and stale-flag conditions, but each clause carries distinct information.

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 read-only lookup with no output schema, the description covers the return shape, the degradation behavior, the meaning of the stale signal, and the boundary conditions where the tool should not be used. Nothing an agent needs to call or interpret the result is missing.

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 meaning beyond it: the fallback rule gives the 'date' parameter behavioral significance, and the returned 'symbol' example (MDX.AX) clarifies how the unsuffixed ticker input relates to the exchange parameter. Currency conversion behavior is left to the schema.

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 (look up) and resource (Yahoo Finance end-of-day close for a listed ticker on a date), and scopes it to listed securities explicitly. An agent can separate this from record_valuation or update_price without opening a schema.

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?

Gives an explicit exclusion set (unlisted trusts, private equity, property) with the reason (no market price, need a statement or valuer's report), which routes the agent elsewhere. It also names the downstream consumer, record_valuation, so the agent knows this is a pricing-evidence lookup rather than a persistence step.

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