Skip to main content
Glama
FEC Checker (French accounting file pre-audit)

FEC Checker (French accounting file pre-audit)

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
lint_fecA

Check a French FEC file's name, encoding, separator, 18 headers and field formats. path is a local path to the FEC (.txt, or a .zip holding one). Returns {ok, file, errors[], warnings[], stats}; each error has a rule code, a count and line numbers. Structural check only; for entry balance, numbering and audit-risk analysis, use the full FEC Checker on Apify: https://apify.com/highfiddle/fec-checker

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of selecting the wrong tool or confusing overlapping purposes. Its description clearly scopes it to structural validation (filename, encoding, separator, headers, field formats).

Naming Consistency5/5

The single name `lint_fec` follows a clear verb_noun snake_case pattern that would scale predictably if more tools were added. No mixed conventions are present.

Tool Count2/5

One tool is too thin for a domain described as 'French accounting file pre-audit', where users reasonably expect balance, numbering and risk checks. The description itself redirects users to an external Apify actor for most of the real work, making the local surface feel like a teaser.

Completeness2/5

Coverage stops at structural linting; there is no entry-balance validation, sequence/numbering continuity check, account or VAT format validation, or any reporting/export operation. The stated dead end ('use the full FEC Checker on Apify') means the tool cannot complete the audit workflow it advertises.

Maintenance

ActivityNo data
ResponsivenessOutdated data