Skip to main content
Glama
Sign In

Untax

by io.untax
OverviewDiscussionsAdmin

get_representation_rules

Read-onlyIdempotent

Look up statutory property tax representation rules, agent licensing requirements, written appearance waiver statutes, and governing boards across states (e.g. TN, GA, FL, TX, NC, AL).

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_representation_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
state_codeNoTwo-letter state postal abbreviation (e.g. 'TN', 'GA', 'FL', 'TX'). Leave empty to retrieve all supported states.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description does not need to restate safety. It adds useful content scope and state coverage, but does not disclose update frequency, authoritative source, or return format.

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 with no filler, and the content scope is presented before the state examples. Every phrase contributes to identifying the resource being looked up.

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?

This is a simple one-parameter lookup tool with rich safety annotations and no output schema. The description adequately explains what categories of rules are returned, though it could say more about the response structure or source authority.

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%, so the state_code parameter and its empty-for-all behavior are already fully documented. The description's state examples reinforce the schema but add no syntax or semantic detail beyond it.

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?

The description states a specific verb, 'Look up,' and a clearly scoped resource: statutory property tax representation rules, agent licensing requirements, written appearance waiver statutes, and governing boards across states. It also names example states, making the tool readily distinguishable from the analytics, audit, and catalog siblings.

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

Usage Guidelines3/5

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

Usage is implied by the statutory-rules domain, but the description does not explicitly say when to use this tool versus another or when it should not be used. It gives clear context but no exclusions or named alternatives.

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