Skip to main content
Glama
Sign In

AccountsOS

by com.accounts-os
OverviewDiscussionsAdmin

Compare Salary And Dividends

compare_salary_dividends
Read-onlyIdempotent

Work out the most tax-efficient mix of salary and dividends for a UK limited company director from the company's profit, against taking it all as salary. An estimate for the current UK tax year. Needs no account.

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": {
      "profit": "<profit>"
    },
    "name": "compare_salary_dividends"
  }
}

Input Schema

NameRequiredDescriptionDefault
profitYesCompany profit before tax, in pounds.
companyNoWhich company to read, by name or id, when the account has more than one (see list_companies). Leave it out to use the only company, or the default.
other_incomeNoOther personal income for the year, in pounds, if any.
has_employment_allowanceNoTrue if the company has other employees and can claim the Employment Allowance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With readOnlyHint, idempotentHint and destructiveHint already declared, the description still adds meaningful behavior: the result is an estimate, scoped to the current UK tax year, and usable without an account. It does not disclose modelling assumptions (e.g. dividend allowance, Employment Allowance effects) or the shape of the returned comparison, leaving a small gap.

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?

Three short sentences with the purpose front-loaded and no filler; the caveats about tax year and no-account follow logically. Slightly cryptic phrasing ('Needs no account') costs a little clarity, but nothing is wasted.

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 a four-parameter, read-only calculation tool with full schema coverage and no output schema, the description covers purpose, scope and the estimation caveat adequately. The remaining gap is that with no output schema it does not hint at what the comparison returns (a savings figure, a breakdown, or a recommendation) or its currency/format.

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 all four parameters are already documented in structured form, and the description only echoes 'from the company's profit'. It adds no extra semantics on how other_income or has_employment_allowance affect the comparison beyond what the schema states, so the baseline 3 applies.

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?

The description states a specific verb and resource — working out the most tax-efficient salary/dividend mix for a UK limited company director — and names the comparison baseline (taking it all as salary). This is clearly distinguishable from siblings like compare_sole_trader_vs_ltd or get_profit_and_loss without opening a 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?

It supplies useful context ('An estimate for the current UK tax year', 'Needs no account'), which tells the agent when the tool is applicable and that no connected account is required. However, it never contrasts itself with alternatives such as compare_sole_trader_vs_ltd, nor does it state exclusions or preconditions beyond the implicit need for a profit figure.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AccountsOS toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources