pnlcs-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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_statsB | Business overview: client, order, invoice and revenue totals. |
| get_healthB | Health of the PNLCS install itself. |
| list_clientsA | List clients, newest first. Optional text search and paging. |
| get_clientA | One client with contacts, by clientid or email. |
| list_client_servicesC | Hosting services that belong to one client. |
| list_client_domainsC | Domains that belong to one client. |
| list_invoicesB | List invoices. Filter by status (draft, unpaid, paid, overdue, cancelled) or client. |
| get_invoiceC | One invoice with its line items. |
| list_ordersA | List orders. Filter by status (pending, active, fraud, cancelled) or client. |
| list_ticketsB | List support tickets. Filter by status. |
| get_ticketB | One ticket with its replies and notes. |
| get_ticket_countsB | Ticket totals per status. |
| list_transactionsB | Payment transactions, newest first. |
| list_productsC | The product catalogue. |
| get_activity_logC | Recent admin and system activity. |
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 15 tools
Each tool targets a distinct resource or summary view: health/stats/activity are clearly separate from client, invoice, order, ticket, transaction, and product listings. There is little overlap, and the get_/list_ split makes singular detail vs collection retrieval obvious.
Tool names consistently use lowercase snake_case with get_ for single items/details and list_ for collections. The compound list_client_services and list_client_domains still follow the same predictable verb_noun pattern as the rest of the set.
Fifteen tools is at the upper end of the ideal range but every one maps to a distinct and useful view of the PNLCS domain, from clients and invoices to tickets and activity. There is no obvious redundancy or filler.
As a read-only business overview server, the surface is broad and coherent: clients, services, domains, invoices, orders, tickets, transactions, products, stats, health, and activity are all exposed. Minor gaps such as no get_order, get_product, or get_transaction detail views, and no mutation endpoints, keep it from being fully complete.