Skip to main content
Glama

List Tax Rules

list_tax_rules
Read-onlyIdempotent

List the verified tax and accounting rules AccountsOS holds for a country, with their keys and summaries: VAT or GST, company tax, income tax, payroll and deadlines. Needs no account: pass country. Use it for any tax question about a named country.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tax_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
countryNoISO country code of the business, such as GB, IE or US. Pass it when the user has not connected AccountsOS. Once connected, leave it out and their company's country is used.
categoryNoOptional category filter. UK categories: vat, corporation_tax, self_assessment, paye, mtd, companies_house, dividends, directors, expenses, capital_gains, capital_allowances, pensions, income_tax, national_insurance, rd_relief. UAE categories: corporate_tax, vat, excise_tax, free_zones, esr, ubo, payroll, compliance. Omit to list all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "ISO country code of the business, such as GB, IE or US. Pass it when the user has not connected AccountsOS. Once connected, leave it out and their company's country is used.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context on top: the rules are curated/"verified" and held by AccountsOS, results carry keys and summaries, and the call works without a connected account. It stops short of saying whether the list is paginated or how large it typically is.

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, front-loaded with what is returned, then the auth-free path, then the use case. Little waste, though the final sentence ("any tax question about a named country") is the least informative and could be replaced by sharper routing guidance.

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?

With no output schema, the description usefully sketches the return shape (rules with keys and summaries) and the no-account calling path. All three parameters are schema-documented and the safety hints are in annotations, so the remaining gap — result volume/ordering and how the category filter interacts with country — is modest for a read-only list tool.

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 coverage is 100%, so country, company and category are fully documented in the schema, including the enum-like category values. The description only reinforces the country parameter ("pass country" when no account is connected) and adds nothing about category or company precedence, so baseline 3 applies.

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?

States a specific verb and resource ("List the verified tax and accounting rules AccountsOS holds for a country") and enumerates the content domains covered (VAT/GST, company tax, income tax, payroll, deadlines). It does not differentiate itself from near-neighbours such as lookup_tax_rule, get_tax_facts or search_tax_facts, so an agent cannot tell from the description alone which of those to pick.

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?

Gives a usable trigger ("Needs no account: pass country") and a use case ("any tax question about a named country"). That last phrase is overbroad rather than exclusive — it claims the whole tax-question space without ruling out the rule-lookup or fact-search siblings, so the guidance is implied rather than discriminating.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.