Skip to main content
Glama
Sign In

Untax

by io.untax
OverviewDiscussionsAdmin

audit_portfolio_batch

Read-onlyIdempotent

Batch ingest and analyze 10–500 properties from CSV text or structured JSON array for real estate agents, listing brokers, and portfolio landlords. Calculates certified comparable sales equity, overassessment delta, estimated annual tax recovery, and ranks top targets.

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

Input Schema

NameRequiredDescriptionDefault
csv_dataNoOptional raw CSV string containing property rows. Headers must include address, city, state, zip.
async_taskNoOptional flag to control background task execution. Batches up to 50 properties run synchronously by default for snappy sub-second responses; larger bulk batches (> 50 properties) automatically run as an asynchronous background task unless async_task is explicitly set to false.
propertiesNoOptional list of property objects with address, city, state, zip, parcel_id, owner_name, current_assessment, building_sqft.
realtor_nameNoOptional name of presenting real estate agent for co-branded executive reporting.
brokerage_nameNoOptional real estate brokerage or investment fund name.
text_addressesNoOptional multiline text string of addresses (one per line) for fast intake.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the batch size band, which is genuine extra context, but says nothing about rate limits, CSV parse failure behavior, or what happens when both csv_data and properties are supplied.

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, then the computed outputs. No filler, though the audience list is slightly ornamental compared to the operational facts.

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?

With no output schema, the description usefully enumerates the four computed results, and it covers intake formats and the sync/async boundary is handled in the schema. Minor tension remains: it demands 10-500 properties while the schema marks all parameters optional, which an agent must reconcile on its own.

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%, so every parameter already carries its own description; the baseline of 3 applies. The description adds the 10-500 volume constraint and confirms CSV text and JSON array are the two accepted intake shapes, but does not explain precedence between csv_data, properties, and text_addresses.

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?

States a specific verb and resource (batch ingest and analyze properties) plus the output set it produces: comparable sales equity, overassessment delta, annual tax recovery, and ranked targets. The 'batch' scope implicitly separates it from the single-property audit siblings, but no sibling is named 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?

Gives audience context (real estate agents, listing brokers, portfolio landlords) and a volume band (10-500 properties), which implies when the tool applies. It never says when not to use it or which sibling to pick for a single parcel versus a portfolio, leaving routing to inference.

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