OpenAccountants

List tax & accounting skills

list_skills

Read-onlyIdempotent

List published OpenAccountants skills with their quality tier and verification status. Optionally filter by jurisdiction (e.g. 'US', 'MT', 'DE', 'GB'), domain (the accounting area, e.g. 'vat-gst', 'payroll', 'income-tax'), or role ('foundation' | 'compute' | 'orchestrator' | 'reference'). Results are paginated (default 100, max 200 per call) — unfiltered browsing of the full ~1,100-skill catalogue requires paging via offset/next_offset, so jurisdiction/domain filters are strongly recommended.

Input Schema

TableJSON Schema

Name	Required	Description
`role`	No	Filter by pipeline role: foundation, compute, orchestrator, reference.
`limit`	No	Max skills to return (default 100, max 200).
`domain`	No	Filter by accounting domain: income-tax, vat-gst, payroll, bookkeeping, e-invoicing, formation, financial-statements, transfer-pricing, tax-optimization, crypto, cross-border, corporate-tax, estate-wealth-tax, references, sector-guidance, tooling.
`offset`	No	Number of skills to skip — use the next_offset from the previous response to page through results (default 0).
`category`	No	(Legacy) display label; prefer domain/role.
`jurisdiction`	No	Filter by jurisdiction code, e.g. 'US', 'MT', 'DE'

Output Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Page size applied to this response.
`total`	No	Total skills matching the filter (across all pages).
`offset`	No	Offset applied to this response.
`skills`	Yes	Matching published skills.
`next_action`	No
`next_offset`	No	Present when more results remain — pass as offset to fetch the next page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedJun 10, 2026

changedInput schema / properties / domain / description

Previous value: -"Filter by accounting domain: income-tax, vat-gst, payroll, bookkeeping, e-invoicing, formation, financial-statements, transfer-pricing, tax-optimization, crypto, cross-border."New value: +"Filter by accounting domain: income-tax, vat-gst, payroll, bookkeeping, e-invoicing, formation, financial-statements, transfer-pricing, tax-optimization, crypto, cross-border, corporate-tax, estate-wealth-tax, references, sector-guidance, tooling."

addedInput schema / properties / limit

Added value: +{
+  "description": "Max skills to return (default 100, max 200).",
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Number of skills to skip — use the next_offset from the previous response to page through results (default 0).",
+  "type": "integer"
+}

addedOutput schema / properties / limit

Added value: +{
+  "description": "Page size applied to this response.",
+  "type": "integer"
+}

addedOutput schema / properties / next_offset

Added value: +{
+  "description": "Present when more results remain — pass as offset to fetch the next page.",
+  "type": "integer"
+}

addedOutput schema / properties / offset

Added value: +{
+  "description": "Offset applied to this response.",
+  "type": "integer"
+}

addedOutput schema / properties / total

Added value: +{
+  "description": "Total skills matching the filter (across all pages).",
+  "type": "integer"
+}

Changed5 schema fields changedJun 9, 2026

changedInput schema / properties / category / description

Previous value: -"Filter by category, e.g. 'international', 'orchestrator'"New value: +"(Legacy) display label; prefer domain/role."

addedInput schema / properties / domain

Added value: +{
+  "description": "Filter by accounting domain: income-tax, vat-gst, payroll, bookkeeping, e-invoicing, formation, financial-statements, transfer-pricing, tax-optimization, crypto, cross-border.",
+  "type": "string"
+}

addedInput schema / properties / role

Added value: +{
+  "description": "Filter by pipeline role: foundation, compute, orchestrator, reference.",
+  "type": "string"
+}

addedOutput schema / properties / skills / items / properties / domain

Added value: +{
+  "description": "Accounting domain facet",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / skills / items / properties / role

Added value: +{
+  "description": "Pipeline role facet",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedJun 2, 2026
- addedOutput schema / properties / next_action
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedMay 24, 2026

changedInput schema / properties / category / description

Previous value: -"Filter by category"New value: +"Filter by category, e.g. 'international', 'orchestrator'"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "skills": {
+      "description": "Matching published skills.",
+      "items": {
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "description": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "display_order": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "jurisdiction": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "tier": {
+            "description": "1 = accountant-verified, 2 = research-verified",
+            "type": "integer"
+          },
+          "verification": {
+            "description": "Verification status summary",
+            "type": "object"
+          }
+        },
+        "required": [
+          "slug",
+          "name",
+          "tier",
+          "jurisdiction"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "skills"
+  ],
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already carry the safety profile (readOnlyHint, idempotentHint, non-destructive, closed world), so the description's burden is lower. It adds genuinely useful behavioral context beyond the annotations: pagination cap of 200, the offset/next_offset paging contract, and the catalogue scale (~1,100 skills) that motivates filtering. No contradiction with annotations.

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?

Core purpose is front-loaded in the first sentence, followed by filters and pagination. Every sentence earns its place — filter examples, role enumeration, pagination limits, and a recommendation. It runs slightly long for a single block, but there is no repetition or filler.

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?

An output schema exists (so return values are documented), annotations cover the safety profile, and the description handles filter options, paging mechanics, and catalogue size. The only notable gap is not explicitly routing agents to search_skills for targeted lookups, but for a filterable list tool the coverage is otherwise strong.

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% and every parameter already has a description, so the baseline is 3. The description adds marginal value by giving concrete example values ('US', 'MT', 'DE', 'GB'; 'vat-gst', 'payroll') and explaining the offset/next_offset paging link that the schema only hints at. The schema still carries the heavy lifting; the description enriches rather than compensates.

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 ('List') and resource ('published OpenAccountants skills') and names the payload ('quality tier and verification status'). The list-vs-search distinction vs. the search_skills sibling is implicit but clear, and the qualifier 'published' adds precision. An agent can tell this from get_skill or search_skills without opening the schema.

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?

Gives concrete, actionable guidance: filter by jurisdiction/domain/role, notes the default/max pagination bounds, and explicitly recommends filters because the ~1,100-skill catalogue 'requires paging via offset/next_offset'. This is clear context on how to call effectively. It lacks explicit exclusions or a when-not-to-use pointer toward search_skills, which keeps it from a 5.

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

All OpenAccountants tools Inspect

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.