Skip to main content
Glama

Lookup Tax Rule

lookup_tax_rule
Read-onlyIdempotent

Look up a verified tax or accounting rule by its key, for any of the 32 countries AccountsOS covers. Needs no account: pass country. Call list_tax_rules first to find the keys. If the country is not covered it says so, and you must not quote another country's rules instead.

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": {
      "key": "<key>"
    },
    "name": "lookup_tax_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe rule key. Use list_tax_rules to see all available keys for the active company's country.
as_ofNoOptional ISO date (YYYY-MM-DD) the answer must be true for. Pass this whenever the question is about a PAST period - a prior-year return, an old invoice, a historic filing - or a FUTURE one such as next year's rates, because rates change and the current rule may not be the one that applies then. The system walks the rule history and returns the version in force on that date, plus the period it applies to. Omit for questions about today: the answer is then the version in force today. A next-year rule may not be law yet; its answer says so.
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.

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

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: no account is required if country is passed, coverage is bounded at 32 countries, and uncovered countries produce an explicit refusal rather than silent fallback. It stops short of describing the response shape or rate/limit behavior, so it is good but not rich.

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?

Three short sentences, front-loaded with purpose, then the prerequisite, then the failure mode. Every sentence carries distinct information and none is 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?

There is no output schema, but the schema's as_of description explains what is returned (the version in force on the date plus its applicable period) and the description explains the uncovered-country case. What is missing is any statement of the response's overall structure, which matters slightly more given the absence of an output schema.

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 the schema descriptions for key, as_of, company and country are already detailed, including the past/future-period rationale for as_of. The description's 'needs no account: pass country' restates what the country schema already says, so it adds little beyond the structured fields. 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?

States a specific verb and resource ('look up a verified tax or accounting rule by its key') plus scope ('any of the 32 countries AccountsOS covers'). It also implicitly distinguishes itself from list_tax_rules by telling the agent to call that tool first to discover keys.

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?

Explicit sequencing ('Call list_tax_rules first to find the keys') and an explicit negative rule ('if the country is not covered it says so, and you must not quote another country's rules instead'). The alternative tool is named with the condition that selects it.

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.

Resources