Skip to main content
Glama
Sign In
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get one check

get_return_check
Read-only

Retrieve full detail for a single return check, including its transactions, help text, decision options, and any recorded answer, using a check key from get_return_checks.

Instructions

One check in full: its lines (the transactions or items behind it), help, decision options and any recorded answer. check_key comes from get_return_checks (e.g. "bank_reconciled:12", "pension_minimum:4").

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>",
      "check_key": "<check_key>"
    },
    "name": "get_return_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
fund_idYesFund ID (discover via whoami or list_funds)
check_keyYesCheck key from get_return_checks
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 declare readOnlyHint=true, so the safety profile is already covered. The description goes beyond that by disclosing the return shape — lines, help text, decision options, and any recorded answer — which is the main behavioral question for an agent inspecting a single check before deciding. It doesn't mention error behavior for invalid keys, so it stops short of a 5.

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?

Two sentences, front-loaded with the resource and payload, then the key provenance. The list of returned components is dense but readable; nothing is filler, though the phrasing is slightly compressed to the point of needing careful reading.

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 the response, and it does so adequately by naming the four components returned. It is complete enough to call correctly; only the behavior on an unknown or out-of-date check_key is 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 100%, so baseline is 3, but the description adds genuine meaning for check_key by showing the composite format with examples ("bank_reconciled:12", "pension_minimum:4"), which the schema only labels generically. fund_id and financial_year are left entirely to the schema, so the gain is partial.

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 ("One check in full") and immediately enumerates the payload — lines, help, decision options, recorded answer. This clearly separates it from the sibling get_return_checks, which lists checks rather than fetching one.

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?

The second sentence routes the agent to get_return_checks as the source of check_key, giving implicit when-to-use guidance (fetch a single check after listing them). It does not state exclusions or what to do if the key is stale, but the retrieval path is unambiguous.

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