Skip to main content
Glama

forecast_truth_in_taxation_bill_shock

Read-onlyIdempotent

Model state Truth-in-Taxation revenue-neutral certified tax rates (T.C.A. § 67-5-1701) against proposed county/city tax rates to forecast individual parcel bill shock and appeal savings before tax bills are mailed.

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": {
      "parcel_id": "<parcel_id>",
      "address": "<address>",
      "prior_appraisal": "<prior_appraisal>",
      "new_appraisal": "<new_appraisal>"
    },
    "name": "forecast_truth_in_taxation_bill_shock"
  }
}

Input Schema

NameRequiredDescriptionDefault
countyNoCounty name (e.g. Hamilton, Knox)
addressYesProperty situs address
parcel_idYesSubject parcel ID
new_appraisalYesNew reappraisal cycle appraised market value
prior_appraisalYesPrior cycle appraised market value

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent, non-destructive, closed-world operation, so the description is not burdened with safety disclosure. Beyond annotations, it adds that the tool models statutory Truth-in-Taxation rates against proposed local rates and forecasts both bill shock and appeal savings, giving useful behavioral context about the nature of the computation.

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 description is a single tightly written sentence that front-loads the core modeling action and statutory basis, then specifies the comparison and forecast outputs. There is no redundant or filler wording.

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 read-only forecasting tool with five fully documented parameters but no output schema, the description supplies the essential context: the statutory model, the rates being compared, and the two forecast outputs. It could say more about assumptions or return structure, but it is complete enough for an agent to understand the tool's role and when to call it.

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 all five parameters are already documented in the input schema. The description adds no parameter-level meaning beyond the schema, such as how prior and new appraisals interact with the modeled rates, so the baseline score of 3 is appropriate.

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 uses a specific verb, 'Model,' and precisely defines the resource and statutory framework: state Truth-in-Taxation revenue-neutral certified tax rates under T.C.A. § 67-5-1701 compared against proposed county/city rates. It also states the concrete outputs, forecasting individual parcel bill shock and appeal savings, which clearly distinguishes it from sibling audit and analysis tools.

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?

The description gives clear contextual guidance by stating the tool is used to forecast parcel-level bill shock and appeal savings 'before tax bills are mailed.' It does not explicitly name when not to use it or point to sibling alternatives, but the intended timing and scenario are sufficiently clear for an agent.

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.