Skip to main content
Glama
Sign In
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Set who signs the declaration or representation letter

update_pack_signatories

Set signatories and signing date for a trustees' declaration or trustee representation letter, including auditor name; an empty list restores default directors. Refused for locked years or finalised documents.

Instructions

Set the signatories (and optionally the signing date) of the trustees' declaration or the trustee representation letter (also the auditor's name for the letter). An empty signatories list returns to the default: the directors present at the year-end trustee meeting. Refused for a locked year or a finalised document.

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

Input Schema

NameRequiredDescriptionDefault
fund_idYesFund ID (discover via whoami or list_funds)
documentYes
reasoningNoWhy you are making this change — recorded on the audit log entry for this write
signed_onNoISO date signed
signatoriesNoWho signs; role defaults to Director/Trustee
auditor_nameNoRepresentation letter only: auditor addressed
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.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false. The description adds meaningful behaviour beyond that: an empty signatories list resets to the default (directors present at the year-end meeting), which is a non-obvious overwrite semantics the agent would not infer from the schema, plus the locked-year/finalised refusal conditions.

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?

Three tight sentences: what is set, the empty-list default behaviour, then the refusal conditions. Front-loaded and every clause carries information, with no restating of the tool name.

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?

For an 8-parameter mutation with no output schema, the description covers the key behaviours: replacement semantics, defaulting, document-specific fields, and guard conditions. It does not say what the call returns or whether it fully replaces versus merges the existing signatory list, which is a minor residual gap.

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 88%, so the baseline is 3. The description earns above that by clarifying that signed_on is optional, that auditor_name applies only to the representation letter, and that an empty signatories array is a reset rather than a no-op — none of which is stated in 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?

States a specific verb (Set) and resource (signatories) and scopes it to two named documents, trustees' declaration and trustee representation letter. It also flags the letter-only auditor field, so an agent can distinguish this from neighbouring write tools like update_trustee_minutes or mark_compliance_document_prepared.

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

Usage Guidelines4/5

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

Gives concrete when-not conditions (locked year, finalised document) and documents the special empty-list case that reverts to default signatories. It stops short of naming an alternative tool or stating the prerequisite workflow for unlocking/reopening, but the usage context is otherwise clear.

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