Skip to main content
Glama
Sign In
finance-engines-mcp

finance-engines-mcp

by Cubiczan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Five-day close workflow

five_day_close

Run the six-gate five-day close to enforce source freeze, subledger cutoffs, reconciliation, evidence, exception SLA, and sign-off. Classifies AP exceptions and returns operator metrics.

Instructions

Run the six-gate five-day close reference: source freeze, subledger cutoffs, reconciliation queue, evidence bundle, exception SLA, and controller sign-off. Classifies AP exceptions when invoices are supplied, optionally flashes covenants, and returns operator metrics (straight-through rate, double-handling minutes, stale-input rate, hours-to-close).

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": {
      "close": "<close>"
    },
    "name": "five_day_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
closeYesClose payload: period {label, period_end}, now (ISO), freeze_at, sources[], cutoffs[], reconciliations[], evidence[], invoices[], optional items/exceptions/signoff/trial_balance/config.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It states actions and outputs but does not disclose side effects, permissions, data mutation, or whether 'flashes covenants' or exception classification writes anything. This is a meaningful gap for a workflow-level operation.

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?

Two sentences pack the gate list, conditional behaviors, and output metrics without filler. The first sentence front-loads the core purpose; the second adds conditional and return details. Slightly dense but well organized.

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?

The description covers the workflow's gates and named metrics, but with no output schema and no annotations it does not explain return structure, side effects, prerequisites, or how the optional covenant/config options are supplied. That leaves an agent with guesses about invocation consequences beyond what is stated.

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?

The single close parameter is already described in the schema with 100% coverage, listing period, now, freeze_at, arrays, and optional fields. The description adds conditional behavior (invoices trigger classification; optional covenant flash) but does not add structural meaning beyond the schema, so baseline 3 is appropriate.

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?

The description opens with a specific verb and resource ('Run the six-gate five-day close reference') and enumerates the six gates, distinguishing it as an end-to-end workflow from focused siblings like close_readiness or classify_ap_exceptions. It also states the conditional classification, covenant flash, and metric outputs, making the tool's role unambiguous.

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 context is implied by the title and gate list: this is for executing the full close workflow. However, the description never explicitly says when to choose it over close_readiness, classify_ap_exceptions, or the covenant tools, nor does it mention excluded scenarios.

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

Deploy Server

Other Tools