Skip to main content
Glama

NovaPixel LexGrid

financial_trend_anomaly

Forensic accounting analysis: CAGR growth, profitability margins (ROE, ROI, ROS, EBITDA Margin), Beneish M-Score for earnings manipulation detection and Benford law distribution test against ATECO benchmarks.

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": {
      "periods": "<periods>"
    },
    "name": "financial_trend_anomaly"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodsYesAt least 2 chronological balance sheet periods
atecoNaceCodeNoSector ATECO/NACE code (e.g. J.62.01, C.25) for industry benchmarks

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 of behavioral disclosure. It names the analytical methods applied, but does not state that the tool is read-only/non-destructive, what data assumptions or minimum-data requirements apply, or what the response contains.

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?

The description is a single dense sentence that is front-loaded with the domain and lists only relevant analyses. It has no filler, though the method list could be easier to scan if separated into smaller phrases.

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?

Inputs are fully described by the schema, and the description identifies the analyses performed. However, with no output schema and no annotations, it should clarify output shape, assumptions, or limitations for a complex forensic-analysis 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 description coverage is 100%, so both parameters are already documented in the schema. The description adds only a small amount by linking the ATECO code to industry benchmarks in the Benford test, without explaining period-to-output mapping or data requirements beyond the schema.

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 clearly frames the tool as forensic accounting analysis and enumerates specific outputs: CAGR growth, profitability margins, Beneish M-Score, and Benford law test. It distinguishes itself by domain from valuation, ESG, and default-prediction siblings, though it lacks an explicit action verb such as 'computes' or 'analyzes'.

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

Usage Guidelines3/5

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

Usage is implied by the forensic-accounting and earnings-manipulation framing, but there is no explicit when-to-use, when-not-to-use, or comparison with alternatives such as dcf_wacc_valuation. An agent can infer the context but receives no routing 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