Skip to main content
Glama

DFX Real Estate Intelligence

by io.github.Capital-W-Holdings
OverviewDiscussionsAdmin

What changed on the private credit tape

search_private_credit_changes
Read-onlyIdempotent

Dated changes by effective date (the quarter end where the change is visible) or by first-seen: new borrowers on any schedule, lenders joining and leaving facilities, facilities leaving every schedule, markdowns across lenders, PIK appearing or rising, a BDC placing a borrower on non-accrual or returning it to accrual (NON_ACCRUAL_PLACED, RETURNED_TO_ACCRUAL, from the BDC's own footnotes), maturities and spreads moving (observed term changes, not amendments), maturities approaching, sponsor x lender pairs forming and repeating. Routine changes (each new piece, increase, decrease, single-lender mark) only with include_routine. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
byNoeffective
limitNo
sinceYesISO date or timestamp.
untilNo
cursorNonext_cursor from a previous page of this tool, unchanged.
dfx_idNoA dfx:pc: id; events where it is the subject or related.
event_typeNo
include_routineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / event_type / enum
      Previous value: -[
-  "NEW_PORTFOLIO_COMPANY",
-  "NEW_CREDIT_POSITION",
-  "POSITION_INCREASED",
-  "POSITION_DECREASED",
-  "POSITION_EXITED",
-  "EXIT",
-  "NEW_LENDER",
-  "LENDER_EXIT",
-  "FAIR_VALUE_DECLINE",
-  "FAIR_VALUE_RECOVERY",
-  "FAIR_VALUE_MARKDOWN",
-  "MATURITY_EXTENDED",
-  "MATURITY_SHORTENED",
-  "PIK_ADDED",
-  "PIK_INCREASED",
-  "COUPON_CHANGED",
-  "SPREAD_INCREASED",
-  "SPREAD_DECREASED",
-  "MATURITY_APPROACHING",
-  "NEW_SPONSOR_LENDER_RELATIONSHIP",
-  "REPEAT_SPONSOR_LENDER_RELATIONSHIP"
-]New value: +[
+  "NEW_PORTFOLIO_COMPANY",
+  "NEW_CREDIT_POSITION",
+  "POSITION_INCREASED",
+  "POSITION_DECREASED",
+  "POSITION_EXITED",
+  "EXIT",
+  "NEW_LENDER",
+  "LENDER_EXIT",
+  "FAIR_VALUE_DECLINE",
+  "FAIR_VALUE_RECOVERY",
+  "FAIR_VALUE_MARKDOWN",
+  "MATURITY_EXTENDED",
+  "MATURITY_SHORTENED",
+  "PIK_ADDED",
+  "PIK_INCREASED",
+  "COUPON_CHANGED",
+  "SPREAD_INCREASED",
+  "SPREAD_DECREASED",
+  "MATURITY_APPROACHING",
+  "NEW_SPONSOR_LENDER_RELATIONSHIP",
+  "REPEAT_SPONSOR_LENDER_RELATIONSHIP",
+  "NON_ACCRUAL_PLACED",
+  "RETURNED_TO_ACCRUAL"
+]
  2. Added

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the full entitlement model: 5-row previews, locked.count/locked.by_type, redaction of contact values and decision-maker names, and the `entitlement`/`locked` fields echoed in every answer. This is unusually rich behavioral context that the annotations cannot convey.

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 dense and the access model is valuable, but the first sentence is a single sprawling run-on enumerating 23 event types, hurting scanability. Front-loading the scope is done reasonably, but the monolithic sentence structure undercuts it.

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?

For an 8-param read tool with no output schema, the description covers what matters: what counts as a change, the routine-event gate, and what the response withholds. Paging semantics (limit/cursor interaction) and full output shape are the only notable omissions.

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 only 38% across 8 params, so the description must carry weight. It does explain the `by` parameter's semantics (effective date = quarter-end visibility vs first-seen) and implies include_routine's role, but since, until, limit, cursor, and dfx_id are left entirely to the 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 states a specific verb+resource (dated changes on the private credit tape) and enumerates the exact change families it surfaces, so an agent knows precisely what it returns. It falls short of 5 because it never names or contrasts a sibling such as search_capital_changes, search_credit_stress, or changes_since, which an agent must disambiguate on its own.

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 gives one real usage rule — routine changes are excluded unless include_routine is set — which is genuinely useful for invocation. However it offers no when-to-use-vs-alternative guidance against the many adjacent change/stress/capital tools, so the agent must infer routing.

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

All DFX Real Estate Intelligence 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