Skip to main content
Glama
Sign In

Tensorust Ontology

by com.tensorust.shop
OverviewDiscussionsAdmin

Loans private credit lenders disagree on

credit_disagreements
Read-only

US companies whose first-lien loan two or more BDC managers mark 10+ points apart at 2026-06-30 (SEC filings), widest gap first: borrower, lowest and highest manager, marks and par. Free: the top 10. full=true: the full list with every fund's mark, par, prior-quarter mark and filing link with a Tensorust key.

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

Input Schema

NameRequiredDescriptionDefault
fullNotrue returns the full list with every fund's mark. Needs a Tensorust key (Authorization: Bearer tdk_...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / full / description
      Previous value: -"true returns the full list with every fund's mark. $0.25 per call over x402, or free with a Tensorust key."New value: +"true returns the full list with every fund's mark. Needs a Tensorust key (Authorization: Bearer tdk_...)."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare this is a read-only, non-destructive, closed-world query. The description adds material behavior beyond them: the free result is capped at 10 rows, full=true requires an Authorization bearer key, and the full result includes per-fund marks, par, prior-quarter marks, and filing links.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core criteria and ordering are front-loaded in the first clause, followed by the free/full distinction and the returned fields. It is dense but purposeful; the colon-separated field list is efficient rather than wasteful.

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?

For a single optional boolean parameter with no output schema, the description is complete: it defines the universe, the disagreement threshold, the as-of date, the sort order, the default free tier, the full tier fields, and the key requirement. An agent has everything needed to choose and call it correctly.

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% and the schema already documents full as a boolean needing a Tensorust key. The description adds useful meaning: full=true expands from the free top 10 to every fund's mark, par, prior-quarter mark, and filing link, while implying the default view is the top 10 only.

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 states a precise resource and filter: US companies whose first-lien loans two or more BDC managers mark 10+ points apart as of 2026-06-30, sorted widest gap first. It also names the returned fields (borrower, lowest/highest manager, marks, par), so an agent can distinguish it from siblings like lender_marks or credit_q3_cuts without opening the schema.

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?

It clearly explains the access tiers: free returns the top 10, while full=true returns the complete list and requires a Tensorust key. It does not explicitly name an alternative sibling tool or a when-not-to-use condition, but the tier guidance gives strong context for invocation.

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

All Tensorust Ontology 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