Skip to main content
Glama

BRAINIAC Accounting Schedules & Close

Rule-based journal anomaly flags

accounting-schedules_journal-anomaly-detect
Read-onlyIdempotent

Flag round amounts, weekend/after-hours postings, amount z-scores, duplicates and Benford first-digit chi-square on journal lines. Price $0.04 USDC. POST /api/v1/accounting-schedules/journal-anomaly-detect. 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": {
      "entries": "<entries>"
    },
    "name": "accounting-schedules_journal-anomaly-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
rulesNorules, object. Required.
entriesYesentries, array. Required.

Output Schema

NameRequiredDescriptionDefault
flagsNoflags. Array.
benfordNobenford. Object.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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.04 USDC, the endpoint is POST /api/v1/accounting-schedules/journal-anomaly-detect, and an unpaid call returns x402 terms without executing — critical for an agent to avoid a false success.

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 capability, then cost, then endpoint, then the payment failure mode. Nothing is padded and each sentence carries operational information.

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?

An output schema exists, so return values need not be described, and annotations cover safety. What remains is the nested entries/rules structure, which the description only gestures at via 'journal lines'; for a tool with nested objects and a payment gate, a brief note on what entries represent would make it fully complete.

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 the baseline is 3. The description does imply that roundAmountMultiple, afterHours/weekendPosting and zScore map to specific named checks, and hints that duplicate and Benford checks run without parameters, but it does not explain the meaning of the rules object or the required entry fields beyond the schema.

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 (Flag) plus the exact anomaly classes it detects — round amounts, weekend/after-hours postings, z-scores, duplicates, Benford chi-square — and scopes them to journal lines. None of the sibling tools (depreciation, reconciliation, trial balance, etc.) do anomaly detection, so an agent can route here unambiguously.

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 naming the input (journal lines) and the checks performed, and the payment precondition is spelled out. However, there is no explicit when-to-use/when-not guidance and no mention of which sibling to pick if the agent instead wants validation or reconciliation.

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