LitVM TCG Oracle

Get Loan Universe

get_loan_universe

The graded slabs the Loan-Terms Oracle will quote, best collateral first: grade, live ask median, census depth, liquidity tier, rank and a free_board flag (the top 250 by census depth carry a free derivation via get_loan_terms_preview). FREE. v2: graded slabs only — raw-card quotes stopped when the USD level froze 2026-09-07.

Returns a PAGE, not the whole book: the full universe is ~1,400 slabs and serialises to ~865 KB, which would swamp an agent's context in one call. total_matching and returned say what you are holding.

limit rows to return (default 50, max 500) tier 'deep' | 'moderate' | 'thin' | 'illiquid' free_board_only True to keep only slabs with a free worked derivation min_value_usd drop slabs whose ask median is below this (0 = no floor)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tier`	No
`limit`	No
`min_value_usd`	No
`free_board_only`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 24, 2026

addedInput schema / properties / free_board_only

Added value: +{
+  "default": false,
+  "type": "boolean"
+}

addedInput schema / properties / limit

Added value: +{
+  "default": 50,
+  "type": "integer"
+}

addedInput schema / properties / min_value_usd

Added value: +{
+  "default": 0,
+  "type": "number"
+}

addedInput schema / properties / tier

Added value: +{
+  "default": "",
+  "type": "string"
+}

AddedSep 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations provided, the description carries full behavioral disclosure. It reveals the tool is FREE, returns a page not the full ~1,400-slab book, warns about ~865 KB serialization, and clarifies that raw-card quotes stopped in v2—exactly the kind of context annotations would otherwise provide.

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

Conciseness5/5

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

The description is dense but every sentence earns its place: purpose is front-loaded, the pagination warning is critical, and the parameter block is compact and scannable. No filler or redundancy.

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?

Given the output schema exists and the description covers pagination and parameter semantics, it is nearly complete. The only gap is that it doesn't explain how to fetch subsequent pages (no cursor or offset parameter is visible), which is a minor omission for a paginated tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates completely: it explains all four parameters (limit, tier, free_board_only, min_value_usd) with types, defaults, allowed values, and meaning. No parameter is left opaque.

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 clearly states the tool returns the graded slabs the Loan-Terms Oracle will quote, with a specific resource and scope. It also distinguishes itself from get_loan_terms_preview by noting the free derivation flag and the v2 shift to graded slabs only.

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 hints that get_loan_terms_preview is the alternative for free derivations on top-250 slabs, and explains the paginated nature of this tool. However, it does not explicitly state when to use this tool versus other siblings beyond that one mention.

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

All LitVM TCG Oracle 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?