Skip to main content
Glama

Get FairPath County Requirements

fairpath_get_county_requirements
Read-only

Return public, CIE-backed county property-tax filing guidance and source metadata. This creates a private FairPath audit record but does not make a filing recommendation or change an external system.

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": {
      "countyId": "<countyId>"
    },
    "name": "fairpath_get_county_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
countyIdYesFairPath county id in the form county_state, for example johnson_ks, cook_il, or harris_tx.

Output Schema

NameRequiredDescriptionDefault
dataYes
redactionYes
sourcesUsedYes
directAnswerYes
evidenceGapsYes
countyCaveatsYes
confidenceLevelYes
complianceFooterYes
informationPostureNoTransitional compatibility field: current broker responses include it, while older broker deployments may omit it during the coordinated rollout.
countyKnowledgeDensityNo
nextAvailableFairPathActionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / countyId / description
      Previous value: -"FairPath county id, such as harris_tx or collin_tx."New value: +"FairPath county id in the form county_state, for example johnson_ks, cook_il, or harris_tx."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations declare readOnlyHint=true, and the description adds genuinely non-obvious context: the call creates a private FairPath audit record and does not modify an external system. That reconciles cleanly with readOnlyHint=true (no external state change) and idempotentHint=false (a record is created per call). It stops short of describing error behavior for unknown county ids, which would be the remaining behavioral gap.

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?

Two sentences, both front-loaded and load-bearing: the first states what is returned, the second states side effects and disclaims recommendations. There is no filler or restatement of the tool name.

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?

The tool is a single-parameter lookup with an output schema, so return-value shape needn't be explained. The description covers what is returned and the audit side effect. The only substantive omission is what happens when the county id is unknown or guidance is unavailable.

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%: the countyId field already documents the required county_state format with concrete examples (johnson_ks, cook_il, harris_tx). The description adds no additional meaning about the parameter, 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 and resource: "Return public, CIE-backed county property-tax filing guidance and source metadata." That is far more informative than the name alone. It doesn't explicitly contrast with siblings like fairpath_check_property or fairpath_explain_evidence_packet, so it earns a 4 rather than a 5.

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: the agent should call this when it needs county-level filing guidance for a given countyId. There is no explicit when-to-use condition, no exclusion, and no pointer to the sibling tools for related tasks, leaving the agent to infer the boundary.

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