Skip to main content
Glama

corporate_default_predictor

Read-onlyIdempotent

[Deterministic insolvency risk assessment. Pure calculation, read-only, side-effect free]. Calculates calibrated Altman Z-Score (differentiated for SMEs, manufacturing, and services), Debt Service Coverage Ratio (DSCR), PFN/EBITDA leverage, Current/Quick Ratio, and 12-24 month default probability under the Italian Corporate Crisis Code (CCII, D.Lgs 14/2019). Usage: Use this tool to predict corporate insolvency risk and assess balance sheet creditworthiness. Do NOT use for earnings manipulation detection (use 'financial_trend_anomaly' instead) or for DCF corporate valuation (use 'dcf_wacc_valuation' instead). Returns: JSON object with { zScore: number, distressZone: 'SAFE' | 'GREY' | 'DISTRESS', defaultProbabilityPercentage: number, dscr: number, pfnEbitdaRatio: number, solvencyStatus: string, alertSignals: string[] }.

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
modelTypeNoSector and firm type model calibrationservices_sme
financialDataYesStandard balance sheet and income statement figures

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds that the calculation is deterministic, pure, and side-effect free, plus the regulatory basis (Italian CCII, D.Lgs 14/2019) that governs the default-probability output. It stops short of stating data-quality or input validation behavior (e.g., what happens with missing or negative figures), which is the one behavioral gap left.

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?

Front-loaded bracket statement, then clearly labelled Usage and Returns sections — easy to scan. The bracketed preamble partly restates the read-only annotation, and the metric list is dense, but every clause carries meaning for tool selection.

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?

No output schema exists, and the description compensates by enumerating the returned JSON fields (zScore, distressZone enum, defaultProbabilityPercentage, dscr, pfnEbitdaRatio, solvencyStatus, alertSignals). Combined with the usage exclusions and regulatory framing, nothing an agent needs to call and interpret this tool is missing.

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 is 100%, so the nested financialData fields and their EUR units are already fully documented. The description adds only the framing that modelType is an Altman model calibration differentiated across SME/manufacturing/services, without explaining which inputs feed which ratio; baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb+resource ('calculates calibrated Altman Z-Score... DSCR... 12-24 month default probability') for a named domain, and explicitly differentiates itself from the two siblings that could be confused with it (financial_trend_anomaly, dcf_wacc_valuation). An agent knows exactly what this tool computes 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 Guidelines5/5

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

The 'Usage' section gives both sides: use it to predict corporate insolvency risk and assess balance sheet creditworthiness, and do NOT use it for earnings manipulation detection or DCF valuation, naming the correct alternative for each. Explicit when/when-not/alternative routing with no gaps.

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