Skip to main content
Glama
Sign In

DFX Intelligence

by io.github.Capital-W-Holdings
OverviewDiscussionsAdmin

One credit provider or BDC in full

get_credit_provider
Read-onlyIdempotent

A credit manager: its classes with basis, the BDCs it advises (from each BDC's own 10-K) with their latest schedules, its credit funds on Form ADV, its sponsor relationships ranked by borrowers financed, and its links to the RIA and private equity graphs by shared CRD or CIK. A BDC: its portfolio every quarter end (fair value, principal held, borrowers, mark on cost, PIK positions, average spread), its largest facilities held with the co-lenders, and the sponsors it finances. Accepts a dfx:pc: provider or BDC id, or a BDC's CIK. 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

NameRequiredDescriptionDefault
detailNocompact: the id, name, type, up to five key facts with their citation and counts of the related rows by type, under 2 KB. research (the default): the full answer.research
dfx_idYesA dfx:pc:<uuid> provider or BDC id, or a BDC CIK number as a string.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / detail
      Added value: +{
+  "default": "research",
+  "description": "compact: the id, name, type, up to five key facts with their citation and counts of the related rows by type, under 2 KB. research (the default): the full answer.",
+  "enum": [
+    "compact",
+    "research"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond the read-only annotations: it explains entitlement gating, row limits for free access, that contact values and decision-maker names are never returned, and that withheld data appears in `entitlement` and `locked` fields. This is exactly the kind of context the annotations do not cover.

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 long and dense, packing many clauses into two sentences. It is front-loaded with what the tool returns, but the access/entitlement paragraph is lengthy and could be tightened without losing 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 the complexity of the response (rich provider/BDC details, entitlement gating) and the absence of an output schema, the description is complete enough to set expectations: it covers the return structure, access limits, and what is withheld, leaving no major gaps for an agent to infer.

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 100%, so parameters are well documented in the schema. The description adds useful clarification on the accepted id formats (dfx:pc: provider/BDC id or BDC CIK) and reinforces the `detail` enum rationale, though it does not go beyond what the schema already provides for `detail`.

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 the specific verb (retrieve) and resource (one credit provider or BDC) and clearly enumerates what the full answer contains, distinguishing it from sibling tools like get_bdc_portfolio or get_credit_facility.

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 states what the tool returns for a provider versus a BDC and specifies accepted id formats, but it does not explicitly tell the agent when to choose this tool over alternatives such as get_bdc_portfolio or get_credit_facility.

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

All DFX 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