Skip to main content
Glama
harshith-vaddiparthy

financial-modeling-harness

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FINANCIAL_HARNESS_WORKSPACENoA private workspace path for the MCP server. If not set, the server uses its default workspace location.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
finance_doctorA

Check local readiness; no model API or external finance account is needed

finance_validateB

Validate inputs, opening balance and provenance. Missing inputs remain errors

finance_runA

Calculate linked monthly statements and named scenarios; save a private immutable run

finance_verifyC

Verify artifact hashes, seven accounting identities and deterministic replay

finance_get_summaryB

Read saved scenario summaries after verifying the run

finance_sensitivityC

Recalculate the full model for up to 20 driver values

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 6 tools

Disambiguation4/5

Each tool maps to a distinct stage of the modeling lifecycle (readiness, validation, run, verification, sensitivity sweep, summary read). The only mild overlaps are doctor vs. validate (both 'checks') and run vs. sensitivity (sensitivity recalculates the model), but the descriptions clearly separate environment readiness from input validation and single-run from driver sweeps.

Naming Consistency4/5

All tools share a `finance_` namespace prefix and use short, readable verb-style suffixes (doctor, validate, run, verify, sensitivity). The only deviation is `finance_get_summary`, which switches to a verb_noun form while others use a bare verb or noun.

Tool Count5/5

Six tools is well within the sweet spot and each one corresponds to a meaningful, non-redundant step in the workflow. There are no filler or trivially thin tools.

Completeness4/5

The surface covers the full lifecycle: readiness check, input validation, model execution, artifact verification, sensitivity analysis, and summary retrieval. Minor gaps exist around managing saved runs (listing or deleting prior immutable runs) and exporting results, but core workflows are covered.

Maintenance

ActivityMaintained
ResponsivenessNo issues