AutoFYI MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| describe_autofyiA | Explain the AutoFYI business rules, safe tool order, and deliberately excluded admin endpoints. |
| autofyi_healthA | Check whether the deployed backend and its FYI browser session are reachable. Makes no changes. |
| get_client_catalog_statusA | Check whether an FYI CSV catalog is published and report its version, age, rows, and columns. |
| describe_client_catalogB | Describe queryable FYI CSV columns. Request one column for up to 10 common values; truncated is not exhaustive. |
| query_client_catalogA | Safely count/filter/group the imported FYI client snapshot. Structured operations only—never raw SQL or live-job claims. |
| search_clientsA | Rank client candidates. Claude compares names, proposes a likely non-exact match, and asks the user to confirm. |
| find_clientA | Load one strict identical client name; otherwise return ranked candidates for AI review and user confirmation. |
| get_client_informationA | Read a selected client's FYI information, Xero templates, and prepared allocations. Use full only when necessary. |
| get_client_jobs_to_invoiceA | Read the live FYI jobs available to invoice and their work amounts. Browser-driven and may take minutes. |
| get_jobs_and_interim_tableB | Read live FYI jobs plus billing-job interim dates and amounts. Makes no FYI changes but may take minutes. |
| inspect_client_billing_stateA | Classify selected live FYI months as unsplit, split, partially allocated, ambiguous, missing, or inconsistent. |
| plan_client_billingA | Build a no-write billing plan from client/Xero/allocation information and identify the next safe live check. |
| prepare_interim_splitB | Validate live FYI interims and prepare—but do not execute—a permanent full-invoice service split. |
| prepare_job_allocationA | Prepare one complete service-type allocation. Merge that service's months/jobs; never mix service types. |
| prepare_direct_invoiceA | Prepare a no-interim direct invoice. Repeating clients are blocked unless the duplicate-billing override is explicit. |
| get_prepared_actionA | Re-read an unexpired prepared action or retrieve its completed result. Never executes it. |
| cancel_prepared_actionA | Cancel a prepared action locally. No request is sent to AutoFYI or FYI. |
| execute_confirmed_actionA | Execute exactly one prepared financial write. Call only after the user supplies the exact preview phrase; never retry. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Most tools have distinct purposes, but search_clients and find_client both handle client lookup with ranked candidates, and get_client_jobs_to_invoice and get_jobs_and_interim_table overlap in reading live FYI jobs. Descriptions help clarify the differences, but an agent could still misselect in some situations.
Tool names generally follow a consistent verb_noun pattern (describe_, get_, prepare_, etc.), with only autofyi_health deviating from the pattern. Minor inconsistencies like singular vs plural (client vs clients) are present but do not cause confusion.
At 18 tools, the set is slightly above the ideal 3-15 range, but each tool serves a distinct step in the billing workflow—from discovery and planning to preparation and execution. The count is justified by the complexity of the domain and the safe execution paradigm.
The tool set covers the full lifecycle for the intended use case: reading client data, inspecting billing state, planning, preparing, canceling, and executing actions. Obvious gaps include a lack of a tool to list all prepared actions, but the core workflows are well covered.