Skip to main content
Glama

BRAINIAC Equity Analytics

Altman Z, Z′ and Z″ scores

equity-analytics_altman-z-score
Read-onlyIdempotent

Compute the public manufacturing Z-score, private Z′ or non-manufacturing Z″ with published safe/grey/distress zones from caller-supplied balance-sheet and income items. Price $0.02 USDC. POST /api/v1/equity-analytics/altman-z-score. An unpaid call returns the x402 payment terms and does not run.

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": {
      "variant": "<variant>",
      "workingCapital": "<workingCapital>",
      "retainedEarnings": "<retainedEarnings>",
      "ebit": "<ebit>",
      "totalAssets": "<totalAssets>"
    },
    "name": "equity-analytics_altman-z-score"
  }
}

Input Schema

NameRequiredDescriptionDefault
ebitYesworkingCapital, number. Required.
salesNosales, number. Optional.
variantYesvariant, string, one of Z, Z_prime, Z_double_prime. Required.
bookEquityNobookEquity, number. Optional.
totalAssetsYestotalAssets, number. Required.
workingCapitalYesworkingCapital, number. Required.
retainedEarningsYesworkingCapital, number. Required.
totalLiabilitiesNototalLiabilities, number. Optional.
marketValueEquityNomarketValueEquity, number. Optional.

Output Schema

NameRequiredDescriptionDefault
zoneNozone. String.
scoreNoscore. Number.
sourcesNosources. Array.
componentsNocomponents. Object.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/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 genuinely non-obvious behavior: a $0.02 USDC price and the x402 gate where 'An unpaid call returns the x402 payment terms and does not run' — a real failure mode worth knowing. It says nothing further about latency, rounding, or error handling beyond payment.

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?

Three short sentences, front-loaded with the computation and variants, then price/endpoint, then the payment failure mode. No filler; every clause carries information an agent needs.

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?

With annotations covering safety, an output schema covering return values, and 100% parameter coverage, the description only needs to explain purpose, variant selection and payment preconditions — all present. The remaining gap is the per-variant required-field mapping, a minor omission for a 9-parameter tool.

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 baseline is 3 and the schema carries the parameter documentation. The phrase 'caller-supplied balance-sheet and income items' adds no mapping of which fields each variant requires (e.g. marketValueEquity for Z vs bookEquity for Z′), which is the one piece of semantic value the description could have supplied.

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 ('Compute the public manufacturing Z-score, private Z′ or non-manufacturing Z″') and even maps each variant to a company type, so an agent knows exactly what is produced. It stops short of differentiating from the scoring-model siblings (Beneish M, Piotroski F), which it could have done in one clause.

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 gives clear selection context by tying each variant to a firm type ('public manufacturing', 'private', 'non-manufacturing'), which effectively tells the caller which enum value to pick. There is no explicit when-not-to-use or routing to the competing scoring tools, so it is clear context rather than full alternative guidance.

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