Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

tax_jurisdiction_lookup

Read-only

Look up tax rates, tax types, and B2B exemptions for a specific jurisdiction code such as US-CA, DE, GB, or AU to apply correct tax rules to a quote or invoice.

Instructions

Look up tax details for a specific region (rate, type, B2B exemptions).

        Args:
            code: Jurisdiction code (e.g. "US-CA", "DE", "GB", "AU").
                Use ``tax_jurisdictions`` to browse all codes.

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": {
      "code": "<code>"
    },
    "name": "tax_jurisdiction_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesJurisdiction code (e.g. "US-CA", "DE", "GB", "AU"). Use ``tax_jurisdictions`` to browse all codes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / code / description
      Added value: +"Jurisdiction code (e.g. \"US-CA\", \"DE\", \"GB\", \"AU\"). Use ``tax_jurisdictions`` to browse all codes."
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful payload context by naming the data returned (rate, type, B2B exemptions), but says nothing about behavior on an unknown or malformed code.

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?

Front-loaded single sentence with the purpose and returned fields, followed by a short Args block. The Args block duplicates the schema description verbatim, which is mild waste but not enough to obscure the core statement.

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 simple read-only lookup with no output schema, the description adequately compensates by naming the return fields and the code format with examples. Only error/empty-result behavior is unaddressed.

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% and the single `code` parameter is documented identically in the schema and the Args block, including the same examples. The description therefore adds no meaning beyond the structured field, which is the expected baseline for a one-parameter tool with full coverage.

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 ("Look up tax details for a specific region") and enumerates the returned fields (rate, type, B2B exemptions), so an agent can tell it apart from tax_jurisdictions. It does not distinguish itself from the related sibling tax_estimate, which is the one remaining ambiguity.

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?

Explicitly routes the agent to tax_jurisdictions when it needs to browse valid codes, which is a concrete when-to-use-alternative. It gives no guidance on when to prefer this lookup over tax_estimate for computing an actual tax amount.

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