Skip to main content
Glama

Financial ratios and health score

lookup_financial_ratios
Read-onlyIdempotent

Financial analysis of a Romanian company: multi-year revenue trend (YoY, 3/5/10-year CAGR), margins, headcount, solvency and liquidity ratios, a 0–100 health score with its rule-by-rule breakdown, red flags, and peer percentiles within the…

Instructions

Financial analysis of a Romanian company: multi-year revenue trend (YoY, 3/5/10-year CAGR), margins, headcount, solvency and liquidity ratios, a 0–100 health score with its rule-by-rule breakdown, red flags, and peer percentiles within the same CAEN activity and county. Verdict: 'growing', 'stable' or 'distressed'. Use lookup_financials for the raw figures.

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": {
      "cui": "<cui>"
    },
    "name": "lookup_financial_ratios"
  }
}

Input Schema

NameRequiredDescriptionDefault
cuiYesRomanian tax identification number (CUI), e.g. '2816464'; 'RO' and leading zeros are accepted.

Output Schema

NameRequiredDescriptionDefault
cuiNoThe firm's CUI.
asOfNoWhat to cite: registry (ONRC snapshot date), financialYear (fiscal year of the figures), anaf (day of the ANAF data), snapshot, published, source.
errorNoSet only when there is no answer (empty_query, invalid_cui, data_unavailable, plan_required ...); such a call is not counted.
flagsNoRed flags.
foundNoWhether any filing is on record.
peersNoPercentiles within the same CAEN activity and county.
totalNoNumber of fiscal years used.
yearsNoPer fiscal year figures and margins.
ratiosNoMargins, equity ratio, debt to equity, liquidity, returns.
sourceNoData source: onrc (registry) or mfp (Ministry of Finance filings).
historyNoYears on record, loss years, revenue peak.
messageNoA sentence for the caller.
signalsNoThe distress signals found.
verdictNogrowing, stable or distressed.
distressNotrue when the distress signals fire.
headcountNoLatest headcount and its change.
attributionNoThe credit line to keep when redistributing the data (CC BY 4.0).
healthScoreNo0-100 score, band and its rule-by-rule components.
revenueTrendNoLatest revenue, YoY growth, 3/5/10-year CAGR, trend label.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.4
    • changedOutput schema / description
      Previous value: -"Derived financial intelligence and a verdict."New value: +"Financial ratios, a health score, peer percentiles and a verdict."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real behavioral content beyond that: the fixed verdict vocabulary ('growing', 'stable', 'distressed'), the rule-by-rule health score breakdown, and that peer percentiles are scoped to the same CAEN activity and county.

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 with the tool's identity and output scope, then closes with the sibling routing sentence. The first sentence is dense with a long enumeration, but each clause carries information an agent needs; no filler sentences.

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?

An output schema exists, so return values need not be explained, yet the description still characterizes the key result fields and the verdict vocabulary, which aids interpretation. For a single-parameter, read-only lookup with full annotations, nothing an agent needs to call or interpret it 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 description coverage is 100% and the single 'cui' parameter is fully documented in the schema, including the 'RO' prefix and leading-zero tolerance. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 and resource ('financial analysis of a Romanian company') and enumerates the exact derived outputs: multi-year trend with CAGR windows, margins, solvency/liquidity ratios, a 0–100 health score, red flags, and peer percentiles. It also names the sibling it differs from, so an agent can separate it from lookup_financials without opening a 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?

Explicitly routes the agent: 'Use lookup_financials for the raw figures,' which gives a clear alternative and the condition that selects it (computed ratios vs. raw figures). It stops short of stating any when-not-to-use case or prerequisites, so it is clear context rather than full routing guidance.

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