Skip to main content
Glama
Sign In
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List the year's audit queries

list_audit_queries
Read-only

Lists audit queries for a fund and financial year, showing each thread's open, resolved, or closed status, answers, replies, and linked program line or return figure.

Instructions

The auditor's queries on a year, each a thread: status open (waiting on the trustee), resolved (answered, waiting on the auditor) or closed (the auditor accepted the answer), the answer, any replies, and the program line or return figure it is about (context). For the trustee's assistant: open ones are yours to answer with answer_audit_query.

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

Input Schema

NameRequiredDescriptionDefault
statusNo
fund_idYesFund ID (discover via whoami or list_funds)
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.17.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, but the description adds real workflow meaning by defining the lifecycle of each status: open waits on the trustee, resolved waits on the auditor, closed means the auditor accepted the answer. That is genuine behavioral context an agent needs in order to interpret results. It omits pagination, ordering, and permission details, which keeps it at 4 rather than 5.

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?

A single dense but well-ordered sentence that front-loads the resource and then the thread contents, followed by one short routing sentence. Every clause carries information: status meanings, answer, replies, and the program-line context; nothing redundant.

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?

There is no output schema, so the description carries the burden of describing return shape, and it does so by listing the fields each query thread contains. For a 3-parameter read tool the coverage is strong; only pagination and result ordering are unaddressed.

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% and the schema already documents fund_id and financial_year, so the description's chief contribution is explaining what the three status enum values actually mean operationally. That is a meaningful addition beyond the raw enum. It adds nothing for the two documented required parameters, but the schema covers those itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource (the auditor's queries on a year) and enumerates what each record contains: status, answer, replies, and the program line or return figure it concerns. The verb 'list' is only implicit in the description (it lives in the title), which keeps it just short of a 5, but an agent can still tell exactly what it retrieves.

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?

It gives role-specific routing: 'For the trustee's assistant: open ones are yours to answer with answer_audit_query', which names a concrete sibling and the condition that selects it. It does not state when-not-to-use or how it relates to other listing tools, so it stops short of fully exhaustive 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