smart-npv-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SMARTNPV_API_KEY | Yes | Your API key from the extended subscription. Required for API calls. | |
| SMARTNPV_BASE_URL | No | The API host. Default is https://www.snpv.co.il | https://www.snpv.co.il |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_clientsA | List clients / leads. Supports paging (limit/offset) and a date range. Prefer a small limit (e.g. 25) — the unfiltered list can be very large. A client is a mortgage case with up to two borrowers: personal fields are suffixed _1 (primary) and _2 (co-applicant). Rows are under 'responseClients'. See docs/client-fields.md for the full field schema. |
| get_clientA | Fetch a single client by uuid or phone. Returns the full record under 'responseClientFields', including both borrowers (_1/_2), employment, income, contract amounts and the last note. See docs/client-fields.md. |
| get_client_documentationsA | List the documents attached to a client (what has been uploaded). |
| create_clientA | Create a new client. Fields go inside params, using the _1/_2 borrower field names from docs/client-fields.md (e.g. firstname_1, phone_1, income_1). |
| update_clientA | Update an existing client by uuid. Fields go inside params, using the _1/_2 borrower field names from docs/client-fields.md. |
| delete_clientA | Delete a client by uuid. Irreversible. |
| add_documentationC | Add a documentation record to a client. |
| upload_documentC | Upload a document file (PDF/PNG/JPG/JPEG) to a client. |
| get_client_statusA | Get the current status/stage of a client. Key for pipeline monitoring. |
| get_status_listA | List the status/stage definitions available in the account. |
| add_statusC | Add or set a status on a client. Fields go inside params. |
| create_productC | Create a product. Fields go inside params. Note: this path (with capital-P 'Products') comes from the vendor docs but has not been verified against the live API yet — confirm with Smart NPV before relying on it. |
| get_client_simulationsB | List a client's mortgage simulations. |
| get_simulationB | Fetch a specific simulation for a client. |
| add_simulationC | Add a mortgage simulation (mix) to a client. |
| delete_simulationA | Delete a simulation. Note: this path (singular 'simulation', not under clients/) comes from the vendor docs but has not been verified against the live API yet — confirm with Smart NPV before relying on it. |
| calc_simulationB | [Premium] Run the reform/recalculation engine on a request payload. |
| get_paymentsA | List a client's payments. |
| add_paymentB | Record a payment on a client (e.g. retainer / installment). |
| update_paymentB | Update an existing payment by payment_uuid. |
| get_contact_groupsA | List contact groups. |
| get_contactsA | List contacts (e.g. bankers, appraisers). |
| add_contactC | Add a contact. Fields go inside params. |
| add_contact_groupC | Add a contact group. Fields go inside params. |
| get_sourcesA | [Premium] List main lead sources (networks). |
| add_sourceB | [Premium] Add a main lead source. Fields go inside params. |
| update_sourceA | [Premium] Update a main lead source. Fields go inside params. |
| balance_report_parsingC | [Premium] Upload a bank balance report PDF for parsing. |
| get_banksA | [Premium] List banks supported by the balance-report service. |
| check_bank_availabilityB | [Premium] Check whether the balance-report service supports a given bank. |
| approval_in_principle_scanningC | [Premium] Upload a bank approval-in-principle document for scanning. |
| get_citiesA | Reference list of cities. |
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 32 tools
Most tools target distinct resources and actions (clients, payments, simulations, contacts). A few document-related tools (upload_document, add_documentation, balance_report_parsing, approval_in_principle_scanning) could cause confusion, but descriptions clarify their specific purposes.
The set uses a mix of get_/list_/check_ and noun-based names (balance_report_parsing), plus add_/update_/create_/delete_. While readable, there is no single consistent verb_noun pattern (e.g., list_clients vs get_banks, check_bank_availability vs get_banks).
32 tools is heavy, exceeding the typical well-scoped range for an MCP server. The server covers many subdomains, but the count feels bloated and detracts from coherence.
Core client lifecycle is covered (CRUD, status, payments, simulations), but there are gaps: no delete_source, no contact update/delete, no payment delete, and some endpoints are unverified. These gaps might force workarounds but do not break the main workflows.