Skip to main content
Glama
thriveventurelabs

AccountsOS MCP Server

Official
by thriveventurelabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Tax Rules

list_tax_rules
Read-onlyIdempotent

Find verified tax and accounting rule keys for UK or UAE, filtered by category, to use with lookup_tax_rule.

Instructions

List all available verified tax/accounting rule keys for the active company's country (UK or UAE), optionally filtered by category. Use this when you need to find the right key for lookup_tax_rule.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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. First observedv0.2.3

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds value beyond annotations by clarifying that the list is scoped to the active company's country (UK or UAE), contains only verified keys, and returns keys rather than full rule details.

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?

Two sentences with no redundancy. The core purpose and scope are stated first, and the usage context relative to lookup_tax_rule is delivered efficiently in the second sentence.

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?

For a simple, optional-parameter list tool with strong annotations, this description is complete. It explains what is returned, the geographic scope, the optional filter, and how the results are meant to be used with lookup_tax_rule.

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%, including a detailed list of valid category values. The description's mention of 'optionally filtered by category' aligns with the schema but adds no new parameter meaning. Baseline 3 is appropriate.

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?

Description states a specific verb ('List') and resource ('verified tax/accounting rule keys for the active company's country (UK or UAE)') with optional category filtering. It explicitly distinguishes itself from lookup_tax_rule by framing its output as the key source for that sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit usage context: 'Use this when you need to find the right key for lookup_tax_rule.' This clearly signals the discovery-then-lookup workflow and leaves no ambiguity about when this tool should be invoked.

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