Skip to main content
Glama
Sign In

Untax

by io.untax
OverviewDiscussionsAdmin

get_jurisdiction_exemption_profile

Read-onlyIdempotent

Retrieve comprehensive statutory exemption rules, local option Senior Freeze ceilings, Disabled Veteran caps, and statutory review dates for any county/state.

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": "get_jurisdiction_exemption_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoState postal code (e.g. 'TN', 'TX', 'IL')
countyNoCounty name (e.g. 'Williamson', 'Davidson', 'Hamilton', 'Knox')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/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 domain context (statutory rules, local option ceilings, review dates) but does not disclose behavior such as what happens if state or county is omitted, error behavior, or response shape.

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?

The definition is a single, front-loaded sentence that packs the key return categories without repetition or filler. Every listed element contributes to understanding what the tool returns.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description adequately covers the data returned for a read-only lookup with two optional parameters, and annotations cover safety behavior. However, with both parameters optional and no output schema, the description does not explain the default scope when state or county is omitted, which is a meaningful gap for correct invocation.

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 already documents the state postal code and county name with examples. The description mentions 'any county/state' but adds no format, default, or interaction semantics beyond what the schema provides, so the 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?

The description uses a specific verb ('Retrieve') and names the concrete resource contents: statutory exemption rules, Senior Freeze ceilings, Disabled Veteran caps, and review dates, scoped to a county/state. It is clear what the tool returns, but it does not explicitly distinguish itself from exemption-related siblings such as verify_va_disability_exemption or audit_disabled_veteran_relief.

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

Usage Guidelines2/5

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

The description states what is retrieved but gives no when-to-use guidance, no exclusions, and no named alternatives. An agent must infer from the tool name and description alone whether this is for jurisdiction-level rule lookup versus parcel-level verification.

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

All Untax toolsInspect
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.

Resources