Skip to main content
Glama
Sign In
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get the trustee minutes / signatory settings

get_year_end_pack_settings
Read-only

Reads recorded content and signatory details for a year-end pack document—trustee minutes, declarations, representation letters, or notes—so you can review it before printing or signing.

Instructions

Read what is recorded for one of the year-end pack's signed documents: trustee_minutes (meeting date, place, chair, attendance with absence reasons, optional standard resolutions, custom resolutions — resolved shows who is present and absent, every resolution as it will print, and the signatories), trustees_declaration and trustee_representation_letter (signatories and signing date; with none set they default to the directors present at the minutes' meeting), or notes_to_financial_statements (events after the reporting date).

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>",
      "document": "<document>"
    },
    "name": "get_year_end_pack_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
fund_idYesFund ID (discover via whoami or list_funds)
documentYes
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.1/5.0
Behavior4/5

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

Annotations only add readOnlyHint=true; the description goes further by documenting a real behavioral default — when signatories are unset they fall back to "the directors present at the minutes' meeting." It also previews what the resolved payload contains (who is present/absent, resolutions as printed, signatories), which matters since there is no output schema. It stops short of noting what happens when a document has never been saved at all.

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

Conciseness3/5

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

The opening clause is correctly front-loaded and nothing is truly filler, but it is one ~90-word sentence threaded with em-dashes and nested parentheses, which forces re-parsing. A bulleted or semicolon-separated breakdown per document type would preserve the content and read far better.

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?

With only three parameters, no output schema and a thin annotation set, the description still covers purpose, per-enum return content and the signatory defaulting rule. An agent has enough to call this correctly and to predict the shape of the response.

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 67%, with fund_id and financial_year already documented in-schema (including the "2023-24" vs numeric id format). The description compensates for the bare document enum by explaining what each of the four values actually returns, which is meaning the schema does not carry.

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 ("Read what is recorded for one of the year-end pack's signed documents") and then enumerates the four document scopes it covers. An agent can distinguish this read tool from siblings like update_trustee_minutes, update_pack_signatories and get_year_end_pack_document without opening any schema.

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

Usage Guidelines3/5

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

Usage is implied by the read-oriented phrasing and the fact that mutation siblings (update_trustee_minutes, update_pack_signatories) exist, but the description never says "use this before updating X" or rules out any alternative. No prerequisites, no ordering guidance relative to list_year_end_pack or get_year_end_pack_document.

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