Tensorust Ontology

Is this federal contractor's lender marking its loan down?

contractor_credit

Read-only

Private credit x federal exposure for one company (name, 12-character UEI or 9-digit EIN): the operating company behind a BDC holdco borrower (resolved through exact name, holdco-stripped name, SAM parent UEI and Form 5500 EIN, with a confidence grade), its federal obligations since FY2025 and DoD FY2024-26 by agency, what every BDC lender marks its first-lien loan at (Jun 30 2026, plus Sep 30 2026 marks pulled from EDGAR as each 10-Q posts), the Q1->Q2 and Q2->Q3 moves, Form 5500 headcount 2024 vs 2025, FCC licenses, turbine aircraft and stress signals. Free: the card. full=true: every lender line with filing link, every recipient UEI, aircraft N-numbers, call signs and up to 17 quarters of mark history with a Tensorust key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "contractor_credit"
  }
}

Input Schema

Name	Required	Description	Default
`full`	No	true returns every linked object and property. Needs a Tensorust key (Authorization: Bearer tdk_...). Omit for the free preview.
`name`	Yes	Contractor or borrower name, UEI or EIN, e.g. 'Peraton', 'Guidehouse', 'Cornerstone OnDemand'

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

changedInput schema / properties / full / description

Previous value: -"true returns every linked object and property. Costs $0.05 per call in USDC on Base over x402 (the tool answers with x402 payment terms that an x402 MCP client pays), or free with a Tensorust key. Omit for the free preview."New value: +"true returns every linked object and property. Needs a Tensorust key (Authorization: Bearer tdk_...). Omit for the free preview."

AddedNov 6, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful context about resolution logic, confidence grades, data sources, and EDGAR freshness, plus the authorization requirement for full results. It does not explain error behavior, rate limits, or what confidence grades mean, so behavioral disclosure is solid but not exhaustive.

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 information-dense but reads as one sprawling sentence packed with domain jargon and many clauses. It is front-loaded with the company and identifier concepts, but it would be much easier to scan if broken into clear sections for inputs, free output, and full output.

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 a two-parameter, read-only lookup tool with no output schema, the description gives substantial detail about what the free card contains and what full mode adds. It covers resolution logic, federal obligations, lender marks, freshness, and authentication, leaving only minor gaps such as confidence-grade interpretation and error conditions.

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 both parameters are already documented, but the description adds formatting specificity for UEI (12 characters) and EIN (9 digits) and explains the resolution paths used for the name. It also elaborates what full=true unlocks beyond the schema's generic 'every linked object and property' wording.

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 resource and scope: private credit plus federal exposure for one company, accepting name, UEI, or EIN. It clearly distinguishes a single-company dossier from aggregate exposure tools, but it does not explicitly name a sibling alternative or contrast its scope with contractor_credit_watch or lender_marks.

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 implies use for a single-company lookup and explains free versus full modes, including that full=true requires a Tensorust key. It does not explicitly say when to use this tool instead of related siblings such as contractor_credit_watch, lender_marks, or credit_q3_cuts, so guidance is implied rather than directive.

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

All Tensorust Ontology tools Inspect

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

Need Help?