Skip to main content
Glama

Hercules property data

by properties.hercules
OverviewDiscussionsAdmin

Get NYC preforeclosure record

get_nyc_preforeclosure_detail

Spends 1 credit, unless this workspace already pulled the record, then free. Returns the full record for one NYC preforeclosure: case and index number, stage, lender, amounts owed and due, mortgage, owner of record and building facts. NYC preforeclosures only; take the id from search_nyc_preforeclosures. Tell the user it costs 1 credit before calling.

Input Schema

NameRequiredDescriptionDefault
idYesThe id of a row from search_nyc_preforeclosures.

Output Schema

NameRequiredDescriptionDefault
balanceYes
propertyYes
alreadyOwnedYes
creditsChargedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / property / properties / marketValue
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
    • changedOutput schema / properties / property / required
      Previous value: -[
-  "id",
-  "bbl",
-  "address",
-  "borough",
-  "indexNumber",
-  "filedOn",
-  "stage",
-  "stageLabel",
-  "equity",
-  "marketValue",
-  "assessedValue",
-  "amountOwed",
-  "units",
-  "yearBuilt",
-  "ownerName",
-  "lender",
-  "latitude",
-  "longitude",
-  "caseCaption",
-  "caseStatus",
-  "borrowerName",
-  "mortgageAmount",
-  "mortgageDate",
-  "amountDue",
-  "amountDueAsOf",
-  "balanceClaimed",
-  "dateOfDefault",
-  "buildingClass",
-  "floors",
-  "lotArea",
-  "buildingArea",
-  "zoning"
-]New value: +[
+  "id",
+  "bbl",
+  "address",
+  "borough",
+  "indexNumber",
+  "filedOn",
+  "stage",
+  "stageLabel",
+  "equity",
+  "assessedValue",
+  "amountOwed",
+  "units",
+  "yearBuilt",
+  "ownerName",
+  "lender",
+  "latitude",
+  "longitude",
+  "caseCaption",
+  "caseStatus",
+  "borrowerName",
+  "mortgageAmount",
+  "mortgageDate",
+  "amountDue",
+  "amountDueAsOf",
+  "balanceClaimed",
+  "dateOfDefault",
+  "buildingClass",
+  "floors",
+  "lotArea",
+  "buildingArea",
+  "zoning"
+]
  2. Changed1 schema field changed
    • changedOutput schema / properties / property / required
      Previous value: -[
-  "id",
-  "bbl",
-  "address",
-  "borough",
-  "indexNumber",
-  "filedOn",
-  "stage",
-  "stageLabel",
-  "equity",
-  "marketValue",
-  "assessedValue",
-  "amountOwed",
-  "units",
-  "yearBuilt",
-  "ownerName",
-  "latitude",
-  "longitude",
-  "caseCaption",
-  "caseStatus",
-  "lender",
-  "borrowerName",
-  "mortgageAmount",
-  "mortgageDate",
-  "amountDue",
-  "amountDueAsOf",
-  "balanceClaimed",
-  "dateOfDefault",
-  "buildingClass",
-  "floors",
-  "lotArea",
-  "buildingArea",
-  "zoning"
-]New value: +[
+  "id",
+  "bbl",
+  "address",
+  "borough",
+  "indexNumber",
+  "filedOn",
+  "stage",
+  "stageLabel",
+  "equity",
+  "marketValue",
+  "assessedValue",
+  "amountOwed",
+  "units",
+  "yearBuilt",
+  "ownerName",
+  "lender",
+  "latitude",
+  "longitude",
+  "caseCaption",
+  "caseStatus",
+  "borrowerName",
+  "mortgageAmount",
+  "mortgageDate",
+  "amountDue",
+  "amountDueAsOf",
+  "balanceClaimed",
+  "dateOfDefault",
+  "buildingClass",
+  "floors",
+  "lotArea",
+  "buildingArea",
+  "zoning"
+]
  3. Changed1 schema field changed
    • changedOutput schema / properties / property / required
      Previous value: -[
-  "id",
-  "address",
-  "borough",
-  "indexNumber",
-  "filedOn",
-  "stage",
-  "stageLabel",
-  "equity",
-  "marketValue",
-  "assessedValue",
-  "amountOwed",
-  "units",
-  "yearBuilt",
-  "ownerName",
-  "latitude",
-  "longitude",
-  "caseCaption",
-  "caseStatus",
-  "lender",
-  "borrowerName",
-  "mortgageAmount",
-  "mortgageDate",
-  "amountDue",
-  "amountDueAsOf",
-  "balanceClaimed",
-  "dateOfDefault",
-  "bbl",
-  "buildingClass",
-  "floors",
-  "lotArea",
-  "buildingArea",
-  "zoning"
-]New value: +[
+  "id",
+  "bbl",
+  "address",
+  "borough",
+  "indexNumber",
+  "filedOn",
+  "stage",
+  "stageLabel",
+  "equity",
+  "marketValue",
+  "assessedValue",
+  "amountOwed",
+  "units",
+  "yearBuilt",
+  "ownerName",
+  "latitude",
+  "longitude",
+  "caseCaption",
+  "caseStatus",
+  "lender",
+  "borrowerName",
+  "mortgageAmount",
+  "mortgageDate",
+  "amountDue",
+  "amountDueAsOf",
+  "balanceClaimed",
+  "dateOfDefault",
+  "buildingClass",
+  "floors",
+  "lotArea",
+  "buildingArea",
+  "zoning"
+]
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses the billing behavior (1 credit), the caching exception (free if the workspace already pulled the record), and an agent-facing obligation to notify the user of cost first. This billing context also explains why the tool carries readOnlyHint=false despite being a GET-style lookup, so an agent won't misread it as a mutation.

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?

Three tight sentences: cost/quality of return first, scope and id source second, user-notification instruction last. Nothing is padded and the most decision-relevant fact (that it costs a credit) is front-loaded.

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?

An output schema exists, so the description need not explain the response shape, yet it still previews the fields. Combined with the id provenance, NYC-only scope, and cost protocol, an agent has everything needed to call this correctly.

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% and the sole parameter is documented at source ('The id of a row from search_nyc_preforeclosures'). The description restates the same origin but adds no format, length, or validity detail beyond the schema, so baseline 3 applies.

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 names a specific verb ('Returns') and resource ('the full record for one NYC preforeclosure') and enumerates the returned fields (case/index number, stage, lender, amounts owed, mortgage, owner of record, building facts). It is immediately distinguishable from the sibling search tools, which return lists rather than a single record.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It scopes the tool ('NYC preforeclosures only'), tells the agent exactly where the required id comes from ('take the id from search_nyc_preforeclosures'), and prescribes an interaction step ('Tell the user it costs 1 credit before calling'). Both the routing condition and the protocol are explicit.

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

All Hercules property data 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