Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
reconcileA

Reconcile expected payments against observed bank-statement entries.

Purpose: Matches expected payment instructions (e.g. from pain.001) against observed bank transactions (e.g. from camt.053) and produces an explainable reconciliation report covering exact matches, short/over adjustments, split settlements (one-to-many), batch credits (many-to-one), and unmatched residuals.

When to use:

  • When performing multi-transaction cash reconciliation between ledgers and statements.

  • When transparent per-match confidence scores and reason breakdowns are required for audit.

When NOT to use:

  • Expects canonical record dicts rather than raw XML; normalize parsed inputs first with normalize_pain001 or normalize_camt053.

  • Evaluates full batches rather than single-pair tuning analysis; use explain_match to inspect one pair.

  • Runs greedy and bounded matching rather than unconstrained combinatorial invoice subsets; use reconcile_many_to_many for subset-sum ILP.

Behavioral transparency: Pure, deterministic, side-effect-free, read-only calculation without network or disk access.

explain_matchA

Explain the match score between one expected and one observed record.

Purpose: Scores a single transaction pair across reference, amount, date, and name signals, returning individual signal weights and an explanation even for pairs below threshold.

When to use:

  • When tuning scoring weights, tolerances, or debugging match decisions.

  • When explaining match confidence for human review or exception handling.

When NOT to use:

  • Scores one pair rather than an entire batch; use reconcile for multi-record batches.

  • Compares amounts directly rather than converting across currencies; use match_amounts_with_fx_drift with an explicit FX rate.

Behavioral transparency: Pure, deterministic, side-effect-free, read-only calculation without external dependencies.

normalize_pain001A

Convert parsed pain.001 payment instructions into canonical expected records.

Purpose: Adapts parsed ISO 20022 pain.001 credit transfer documents or transaction lists into canonical expected records ready for the reconcile engine.

When to use:

  • When converting parsed pain.001 files into canonical expected records for reconcile.

  • When mapping diverse payment field structures into uniform id, amount, and reference fields.

When NOT to use:

  • Accepts parsed pain.001 payment orders only, not bank statement entries (camt.053); use normalize_camt053 for statements.

  • Expects a parsed dictionary or list rather than raw XML text.

Behavioral transparency: Pure, deterministic, read-only data normalization.

normalize_camt053A

Convert parsed camt.053 statement entries into canonical observed records.

Purpose: Adapts parsed ISO 20022 camt.053 bank statement documents or entry lists into canonical observed records ready for the reconcile engine.

When to use:

  • When converting parsed bank statements into canonical observed records for reconcile.

  • When transforming bank booking entries into uniform id, amount, date, and counterparty fields.

When NOT to use:

  • Accepts parsed camt.053 bank statements only, not payment initiation orders (pain.001); use normalize_pain001 for payments.

  • Expects a parsed dictionary or list rather than raw XML text.

Behavioral transparency: Pure, deterministic, read-only data normalization.

list_sandbox_scenariosA

List built-in sandbox reconciliation scenarios and magic references.

Purpose: Returns the catalog of deterministic test-mode scenarios and synthetic magic references to demonstrate reconciliation outcomes without production data.

When to use:

  • When discovering available test scenarios (e.g. clean_match, month_end, fx_drift).

  • When testing agent decision-making workflows with zero setup.

When NOT to use:

  • Returns static synthetic test fixtures only, not production reconciliation batches.

Behavioral transparency: Static catalogue retrieval; read-only and instantaneous.

load_sandbox_scenarioA

Load expected and observed record inputs for a named sandbox scenario.

Purpose: Retrieves the test-mode expected and observed fixture records for a named scenario so they can be inspected, customized, or passed to reconcile.

When to use:

  • When reviewing fixture data prior to executing reconciliation runs.

  • When creating custom variations of standard reconciliation scenarios.

When NOT to use:

  • Returns raw fixture inputs without running matching; use run_sandbox_scenario to load and reconcile a scenario in one step.

  • Requires a registered scenario name from list_sandbox_scenarios.

Behavioral transparency: Deterministic dictionary lookup; read-only with no side effects.

run_sandbox_scenarioA

Load a named sandbox scenario and immediately return its reconciliation report.

Purpose: One-call execution that loads built-in fixture records and executes the reconciliation pipeline, returning a complete explainable match report.

When to use:

  • When performing quick verification, smoke tests, or initial agent demonstrations.

  • When verifying tolerance tuning against standard test cases.

When NOT to use:

  • Operates on built-in synthetic fixtures rather than live production data.

  • Uses fixed scenario inputs; use reconcile to supply custom expected and observed records.

Behavioral transparency: Deterministic, in-memory execution; read-only and idempotent.

match_names_probabilisticA

Score two counterparty names using Jaro-Winkler string similarity.

Purpose: Computes similarity in [0, 1] between two company or individual names, tolerating typographical variations and legal suffix abbreviations (e.g. 'Corp' vs 'Corporation Inc').

When to use:

  • When verifying whether two counterparty or entity names represent the same party.

  • When evaluating name similarity thresholds for automated matching rules.

When NOT to use:

  • Scores counterparty name strings in isolation rather than full multi-signal transaction records; use reconcile or explain_match for full records.

  • Accepts string inputs only.

Behavioral transparency: Pure, deterministic string calculation; read-only and idempotent.

match_amounts_with_fx_driftA

Compare two amounts in different currencies within an FX drift tolerance.

Purpose: Converts currency amounts using a provided exchange rate and verifies if the percentage difference falls within an acceptable tolerance window using exact decimal arithmetic.

When to use:

  • When reconciling cross-currency payments with conversion timing or rate variance.

  • When evaluating FX tolerance bounds on cross-border transactions.

When NOT to use:

  • Designed for cross-currency comparisons with a positive fx_rate; use reconcile for same-currency tolerance matching.

  • Rejects zero or negative FX rates.

Behavioral transparency: Pure mathematical calculation; read-only and idempotent.

reconcile_many_to_manyA

Match statement deposits to disjoint subsets of invoices via subset-sum ILP.

Purpose: Solves bounded subset-sum as an integer linear program (ILP) to pair statement deposits against matching combinations of outstanding invoice records.

When to use:

  • When customer deposits consolidate multiple invoices or split remittances.

  • When one-to-one or one-to-many heuristics leave unmatched aggregates.

When NOT to use:

  • Solves combinatorial subset-sum rather than standard 1:1 or 1:N reconciliation, where reconcile is faster.

  • Requires the optional ilp extra (pip install reconcile-mcp[ilp]).

Behavioral transparency: Deterministic ILP optimization; read-only and idempotent.

Prompts

Interactive templates invoked by user choice

NameDescription
reconcile_workflowStep-by-step guidance for driving an end-to-end ISO 20022 reconciliation with these tools, from raw pain.001/camt.053 through to an explained match report.

Resources

Contextual data attached and managed by the client

NameDescription
sandbox_scenarios_resourceThe catalogue of built-in sandbox scenarios and magic references, as JSON -- the resource form of `list_sandbox_scenarios`.

TDQS

A4.4/5.0

Scored across 10 tools

Disambiguation5/5

Each tool has a sharply bounded role, and descriptions explicitly cross-reference the alternative tool to use instead (e.g. reconcile vs reconcile_many_to_many vs explain_match, list/load/run_sandbox_scenario). Overlap-prone pairs are differentiated by input shape, scope, and output, so misselection is unlikely.

Naming Consistency4/5

Consistent snake_case with verb-first naming (normalize_pain001, match_names_probabilistic, run_sandbox_scenario, reconcile_many_to_many). Minor deviations: the bare `reconcile` verb and adjective suffixes like `_probabilistic`/`_with_fx_drift` break the strict verb_noun rhythm.

Tool Count5/5

Ten tools is well within the ideal range and every tool earns its place: normalization, core matching, pair-level explanation, specialist matchers, and sandbox fixtures. No redundant wrappers or filler tools.

Completeness4/5

Covers the full lifecycle: ingest normalization for both ISO 20022 directions, batch and pairwise matching, FX and name signals, ILP subset matching, and sandbox fixtures for testing. Minor gaps exist around report export/persistence and other message types (e.g. pain.002, camt.052), but core workflows have no dead ends.

Maintenance

ActivityActive
ResponsivenessOutdated data