Skip to main content
Glama

NovaPixel LexGrid

corporate_default_predictor

Deterministic financial insolvency predictor calculating Altman Z-Score (differentiated for SMEs, manufacturing and services), DSCR, PFN/EBITDA, Current/Quick Ratio and 12-24 month default probability.

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": {
      "financialData": "<financialData>"
    },
    "name": "corporate_default_predictor"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelTypeNoservices_sme
financialDataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does usefully disclose determinism (reproducible, non-LLM arithmetic) and the differentiated model families, which is real behavioral context. It does not disclose currency/units, how missing optional inputs are handled, how the default probability is derived, or any error behavior for degenerate inputs such as zero denominators.

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?

A single dense sentence that front-loads the core function and then lists outputs; no filler. It is tightly written, though the parenthetical model differentiation interrupts the flow and the metric list is long enough to read as a spec dump.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lists the computed outputs, which partially compensates for the missing output schema, and names the input domain (financial statements). Given a nested 14-field object and no annotations, it is still incomplete: model selection logic, unit/currency expectations, and which fields are mandatory for which ratios are all left unstated.

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 for the top-level modelType is absent, and the description partially compensates by stating that the calculation is differentiated for SMEs, manufacturing and services, which hints at model selection. It does not map the enum values (services_sme, manufacturing_private, manufacturing_public) to their intended use, nor explain that the required seven fields drive the Altman Z-Score while optional fields feed DSCR, PFN/EBITDA and liquidity ratios.

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 names a specific verb and resource (insolvency prediction) and enumerates exactly which metrics are computed (Altman Z-Score, DSCR, PFN/EBITDA, Current/Quick Ratio, 12-24 month default probability). It is clearly distinguishable in substance from csrd_esg_calculator, dcf_wacc_valuation and financial_trend_anomaly, but no sibling is named, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no indication of what distinguishes this from a valuation or ratio-analysis alternative. An agent knows what the tool computes but not when it should be preferred over dcf_wacc_valuation or financial_trend_anomaly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources