Skip to main content
Glama

Explain A FairPath Evidence Packet

fairpath_explain_evidence_packet
Read-only

Explain the evidence categories FairPath can organize into a homeowner-reviewed property-tax evidence packet. This creates a private FairPath audit record but does not recommend a filing position, predict an outcome, or change an external system.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With readOnlyHint=true, destructiveHint=false, and openWorldHint=false already supplied, the description adds real context the annotations cannot: it discloses that the call creates a private FairPath audit record, and it rules out three plausible-but-wrong behaviors (filing recommendations, outcome predictions, external system changes). That is meaningful side-effect and scope disclosure beyond the structured hints.

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?

Two sentences, front-loaded with the action and scope, followed by the disclaimer. The second sentence is somewhat long but each clause (audit record, no recommendation, no prediction, no external change) carries distinct information an agent needs.

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?

An output schema exists, so return values need not be explained, and the empty parameter list means there is no input complexity to cover. The remaining minor gap is that the description never says how a packet with no parameters relates to a specific property or homeowner, which is the one question an agent might still have.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a 0-parameter tool applies. Nothing in the description contradicts or confuses the empty schema.

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 opens with a specific verb and resource: 'Explain the evidence categories FairPath can organize into a ... evidence packet.' That is concrete enough to distinguish it from fairpath_check_property and fairpath_get_county_requirements, which are clearly different resources. It stops short of 5 because it never names or contrasts with those siblings explicitly.

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 only implied: an agent can infer this is the tool for understanding what evidence categories exist before/alongside a packet. There is no explicit 'use this when...' or 'use X instead when...' guidance. The negative scoping ('does not recommend a filing position, predict an outcome') does helpfully bound what the agent should not expect from it, which lifts it above 'no guidance'.

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