Skip to main content
Glama

parcel-edge

by com.dropwatchhq

lien_bundle_report

INVESTOR DESK (paid, $0.50 USDC/call; free preview): per-parcel tax-deed title-research report for a single Allegheny County PA PIN. Returns every UNSATISFIED County/School/Municipal tax lien on the parcel bundled into one surviving-lien stack with a per-taxing-body split + total, the tax-year span (a long tail signals a likely JUDICIAL 'free & clear' sale; a short one an UPSET sale where the buyer takes SUBJECT to surviving liens), and the PA statutory redemption posture (72 P.S. §5860 — PA has no general post-sale redemption; the risk is surviving liens). The cross-join a tax-deed investor pays $150–500/parcel for. CANDIDATE title input, NOT a title opinion — confirm sale type + named lienholders with the county/counsel before bidding.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pinYesAllegheny County PIN (parcel ID), e.g. 0138S00120000000.

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description fully bears the burden. It details the report's contents (unsatisfied lien stack, per-tax body split, tax-year span, redemption posture) and limitations (not a title opinion). It does not mention error handling or data freshness but is otherwise transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose (5 sentences) including technical details like statutory references and cost comparisons. Although front-loaded with key info, it could be more concise without losing essential meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description comprehensively explains the return values (surviving lien stack, per-tax body split, tax-year span interpretation, redemption posture) and provides usage warnings. It is complete for an agent to decide invocation and interpret results.

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?

The single parameter 'pin' has schema coverage of 100% with an example. The description adds that it's for a single Allegheny County PA PIN, which is consistent but does not add substantial value beyond the schema.

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 clearly states it provides a per-parcel tax-deed title-research report for a single Allegheny County PA PIN, returning unsatisfied tax liens. It specifies the verb 'returns' and the resource 'report', and distinguishes itself from siblings (other tools are about leads, flags, etc.) and from a title opinion.

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 provides context: it's an investor desk tool, paid with free preview, and warns it's a candidate input not a title opinion, advising confirmation with county/counsel. It does not explicitly state when not to use or alternative tools, but the specialization makes misuse unlikely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All parcel-edge toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a distinct aspect of property data: permit windows, stalled projects, exemption flags, lien reports, overassessment leads (commercial vs single parcel), and county metadata. The descriptions clearly differentiate their purposes, with no functional overlap.

Naming Consistency5/5

All tool names use a consistent underscore_case pattern with descriptive noun phrases (e.g., construction_window_leads, exemption_flags). No mixed conventions or cryptic abbreviations are present.

Tool Count5/5

Seven tools provide a well-scoped set for the server's purpose (property analytics for various stakeholders). Neither too few nor too many—each tool serves a clear, distinct function.

Completeness4/5

The tool set covers core workflows for permit tracking, exemption auditing, lien analysis, and overassessment detection. Minor gaps exist (e.g., no general property detail lookup), but the server seems intentionally focused on lead generation and flagged issues.

Resources