Skip to main content
Glama

BRAINIAC Equity Analytics

Beneish eight-variable M-score

equity-analytics_beneish-m-score
Read-onlyIdempotent

Compute DSRI, GMI, AQI, SGI, DEPI, SGAI, LVGI and TATA and the Beneish (1999) M-score with the −1.78 flag threshold. Price $0.03 USDC. POST /api/v1/equity-analytics/beneish-m-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": {
      "current": "<current>",
      "prior": "<prior>"
    },
    "name": "equity-analytics_beneish-m-score"
  }
}

Input Schema

NameRequiredDescriptionDefault
priorYescurrent, object. Required.
currentYescurrent, object. Required.

Output Schema

NameRequiredDescriptionDefault
mNom. Number.
flagNoflag. Boolean.
indicesNoindices. Object.
sourcesNosources. Array.
thresholdNothreshold. Number.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral facts: the call costs $0.03 USDC, is served via POST at a specific path, and an unpaid invocation returns x402 payment terms instead of a result. That payment precondition is exactly the kind of context annotations cannot express.

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 tight sentences with zero waste: the output, the threshold, the price, the endpoint, and the failure mode, in that order. The endpoint string is mildly redundant with the tool name but is a legitimate operational detail for direct HTTP use.

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?

Return values are covered by the output schema and the payment/auth behavior is disclosed, but a computation tool with two nested objects of ~25 optional numeric fields each should say which fields are actually needed for a valid M-score and what happens when some are omitted. Without that, an agent cannot tell whether a three-field payload yields a score, nulls, or an error.

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 both required parameters (current, prior) are documented in the schema, so the baseline of 3 applies with no parameter content in the description. Some value is left on the table: the schema field descriptions are tautological ('cfo, number. Optional.'), so nothing anywhere tells the agent which balance-sheet/income-statement fields each of the eight ratios actually consumes.

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?

Names the exact artifact produced (the eight Beneish variables DSRI, GMI, AQI, SGI, DEPI, SGAI, LVGI, TATA plus the M-score) and cites the model vintage and the −1.78 flag threshold, so an agent knows precisely what comes back. It stops short of differentiating itself from the conceptually adjacent siblings (piotroski-f-score, altman-z-score), so it lands at clear-but-undifferentiated.

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?

The description never states when to reach for this over equity-analytics_piotroski-f-score or equity-analytics_altman-z-score, nor what screening question the M-score answers (earnings manipulation). The only conditional language is operational — what happens on an unpaid call — not usage 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