Skip to main content
Glama

One building's financing and ownership chain

get_re_property_chain
Read-onlyIdempotent

A building's recorded NYC mortgages, satisfactions and assignments (parties as filed), the sponsor resolved behind an owner of record when owner_ids are given, its CMBS notes (lender = originator, holder = the trust, special servicer, balance, maturity, status, the annex's borrower LLC and sponsor), its accepted owner chain with the basis's measured precision, fund holdings bound to it and fund loans on its address. property is the street address or building name; property_dfx_id comes from resolve_address. ACCESS: without a paid DFX plan on the vertical, a list returns its first 5 rows in full and a count of the rest by type (locked.count, locked.by_type), never the rows; a record names its subject and the first 3 related names per section; contact values (email, phone, profile URLs) and decision-maker names are never returned, only their types and counts. Every answer says what it withheld in entitlement and locked. Full access: DFX Intelligence, 7 days free at https://dfxintel.com/data-factory/plans.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
propertyNo
owner_idsNoOwner of record dfx ids from get_property_record, to read the sponsor resolved behind each.
property_dfx_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only cover the read-only/idempotent safety profile, and the description goes well beyond them: it discloses the entitlement truncation behavior (first 5 rows plus locked.count/locked.by_type), the record-level 3-related-names cap, that contact values and decision-maker names are never returned, and that every response reports withholding via `entitlement` and `locked`. This is exactly the kind of non-obvious behavioral context an agent needs before calling.

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 content is front-loaded (what is returned, then ACCESS rules, then plan plug), which is good. But the first sentence is a ~100-word run-on enumerating every section, and the closing promotional sentence is padding. Information-dense but poorly structured and longer than needed.

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 must describe returns, and it does: it names the sections, the response meta-fields (`entitlement`, `locked`), and the truncation semantics under gating. A 4-param tool with 0 required params is covered well; only the `limit` parameter's behavior is unaddressed.

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?

Schema coverage is only 25% (only owner_ids is documented inline), so the description carries weight and largely delivers: it defines `property` as a street address or building name and `property_dfx_id` as coming from resolve_address, and the owner_ids sourcing is covered. The `limit` parameter is left unexplained in both the schema and the description, which is the remaining gap.

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?

Names a specific resource (one building's NYC mortgages, satisfactions, assignments, CMBS notes, owner chain, fund holdings/loans) with concrete sub-fields enumerated. It is clearly distinguishable from siblings like get_property_record or get_re_org_chain because it scopes everything to a single building and lists exactly what sections come back.

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?

It routes the agent to sibling tools for inputs (property_dfx_id from resolve_address, owner_ids from get_property_record), which implies when the tool is applicable. However, it never states when to prefer this over get_property_record, get_re_org_chain, or search_cmbs_loans, and gives no exclusions or preconditions beyond the gating model.

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.