Skip to main content
Glama
Sign In
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Find a page in the web app

find_page
Read-only

Locate pages, menu paths, and URLs in Beeswax Shares for reports, views, and actions. Pass search terms and optional fund or record IDs to get ready-to-click links instead of guessing app URLs.

Instructions

Find where something is in the Beeswax Shares (Alpha) web app: the page that shows a report or view, where it sits in the menus, what it shows, and its URL. Use whenever the user asks where to see, find, check, sign or do something in the app, or when you tell them to open a page — never construct or guess an app URL yourself. Pass a few words in query (e.g. "operating statement", "member balances", "sign off", "bank feed", "API token"); omit it to get the whole map. Pass fund_id (and optionally financial_year, holding_id, bank_account_id) to get ready-to-click urls; otherwise pages come back as url_templates listing the ids they needs. For one specific record (a holding, transaction, bank account, return section or field, check) use the web_url on that record from the tool that returned it instead.

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

Input Schema

NameRequiredDescriptionDefault
queryNoWords describing what the user wants to see or do; all must match
fund_idNoFund ID, to fill the fund into page URLs
holding_idNoHolding ID, for holding pages
financial_yearNoFinancial year label "2025-26" or id; defaults to the fund's current year
smsf_return_idNoAnnual return ID; defaults to the financial year's current return, if one has been started
bank_account_idNoBank account ID, for account pages

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.8.1

TDQS

A4.7/5.0
Behavior5/5

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

Because there is no output schema, the description carries the burden and does so well: it discloses that omitting `query` returns the whole map, that supplying fund_id (and optional year/holding/account ids) yields ready-to-click `url`s versus `url_template`s that list the ids they `needs`. That is real behavioral context beyond the readOnlyHint annotation.

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?

Dense and front-loaded, with the core purpose in the first clause and routing advice after. It is on the long side and packs several ideas into one paragraph, but nearly every sentence adds actionable information.

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?

With six optional parameters and no output schema, the description supplies the return-value shape (urls vs url_templates) and the omit-query behavior, which is what an agent needs to call it correctly. The only gap is explicit treatment of `smsf_return_id`.

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%, but the description still adds meaning: `query` is 'a few words' with all terms matching, and omitting it returns the whole map; the id parameters interact to produce concrete urls. It slightly under-documents `smsf_return_id` (only implied via 'return section'), keeping it below a 5.

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?

States a specific verb and resource ('Find where something is ... the page that shows a report or view, where it sits in the menus, what it shows, and its URL'). This clearly distinguishes it from data-returning siblings like list_funds or get_portfolio — it is a navigation/locator tool, not a data tool.

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 explicit when-to-use ('whenever the user asks where to see, find, check, sign or do something in the app, or when you tell them to open a page'), an explicit prohibition ('never construct or guess an app URL yourself'), and an explicit alternative for single records ('use the web_url on that record from the tool that returned it instead').

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