Skip to main content
Glama
Sign In
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get the year-end pack as a PDF

get_year_end_pack_pdf
Read-only

Generate and save a fund's full year-end pack—or a single document—as a PDF to your computer, returning the file path and size.

Instructions

Render the whole year-end pack (cover, contents and every document) — or one document — as a PDF and save it on this computer (BEESWAX_EXPORT_DIR, default ~/Downloads/beeswax-shares). Returns the file path and size. Document keys come from list_year_end_pack; member_statement also needs member_id.

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

Input Schema

NameRequiredDescriptionDefault
fund_idYesFund ID (discover via whoami or list_funds)
documentNoOne document only; omit for the whole pack
member_idNoMember ID, for document member_statement
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.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true. The description adds genuinely useful behavior: the file is written to disk at BEESWAX_EXPORT_DIR (default ~/Downloads/beeswax-shares) and the result includes path and size. It doesn't cover overwrite behavior, size/runtime for rendering the full pack, or what happens on partial failure, so it is strong but not complete.

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?

One dense sentence plus one clarifying sentence, front-loaded with the primary action and scope. Every clause carries information an agent needs: scope, destination, return values, and key sourcing. No redundancy with the title.

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?

No output schema exists, and the description compensates by stating that the return value is the file path and size. Combined with the export directory and the parameter dependency note, an agent has everything needed to call this correctly on the first attempt.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description does add value beyond the schema by stating the cross-parameter dependency (member_statement requires member_id) and by pointing at list_year_end_pack as the source of valid document keys — a conditional rule the schema itself cannot express.

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: 'Render the whole year-end pack (cover, contents and every document) — or one document — as a PDF.' The scope distinction (whole pack vs single document) plus the explicit contrast with list_year_end_pack and get_year_end_pack_document makes it easy to separate from siblings.

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 clear operating context: omit 'document' for the full pack, and a document key is required to target one. It points at list_year_end_pack as the source of keys and names the member_statement caveat. It does not explicitly say when to prefer this over get_year_end_pack_document or download_document, so it stops short of full routing guidance.

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