tryton-stock-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRYTON_HOST | No | Tryton host | localhost |
| TRYTON_PORT | No | JSON-RPC port | 8000 |
| TRYTON_USER | Yes | Dedicated read-only user | |
| TRYTON_TIMEOUT | No | Request timeout in seconds | 30 |
| TRYTON_DATABASE | Yes | Tryton database name | |
| TRYTON_PASSWORD | Yes | User password | |
| TRYTON_PROTOCOL | No | http or https | http |
| TRYTON_AUDIT_LOG | No | Log destination | ./logs/mcp_actions.jsonl |
| TRYTON_AUDIT_LOG_ENABLED | No | Enable metadata-only local logging | true |
| TRYTON_ALLOW_INSECURE_REMOTE | No | Permit HTTP to a non-local host | false |
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 |
|---|---|
| audit_product_historyB | Audit a product's complete stock history by name, code or ID. If a name or lot matches multiple records, the result asks the caller to choose one candidate before the full audit runs. |
| get_tryton_contextB | Check the configured connection and required Tryton model access. |
| describe_modelA | Describe fields for any model; this returns metadata, not records. |
| search_productsA | Search product variants by name or code. |
| get_product_detailB | Return relevant fields for one product variant. |
| search_lotsC | Search stock lots by text and/or product. |
| get_lot_detailC | Return identifying information for one stock lot. |
| search_locationsA | Search stock locations by name, code or type. |
| get_location_detailB | Return relevant information for one stock location. |
| search_stock_movesC | Search stock moves with product, lot, state and location filters. |
| get_stock_move_detailB | Return principal and diagnostic fields for one stock move. |
| find_non_done_movesB | Find moves that are neither done nor cancelled. |
| summarize_product_movesC | Summarize a product's movement history and suspicious signals. |
| compare_products_stock_historyC | Compare movement histories for multiple product variants. |
| search_reference_globallyB | Search a textual reference across the approved stock-audit models. |
| summarize_product_location_flowsC | Summarize entries, exits and internal location flows for a product. |
| reconstruct_product_stock_ledgerC | Reconstruct a chronological diagnostic ledger from stock moves. |
| find_negative_lot_location_balancesC | Find negative derived balances across products, lots and locations. |
| get_official_product_quantityC | Read Tryton's contextual product quantity for one location. |
| analyze_stock_move_root_causeB | Collect read-only causal context around one stock move. |
| generate_move_root_cause_reportB | Return JSON evidence and Markdown for one stock move investigation. |
| generate_product_negative_stock_reportC | Return JSON evidence and Markdown for negative derived balances. |
| generate_product_stock_audit_reportC | Return a comparative stock audit as JSON and Markdown. |
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 23 tools
Core entity tools (search/get for products, lots, locations, moves) are clearly separated, but the audit/summary/report cluster overlaps: audit_product_history, summarize_product_moves, reconstruct_product_stock_ledger, and generate_product_stock_audit_report all deal with product movement history and could be misselected. Descriptions help, but boundaries are not crisp.
All names are snake_case verb_noun and follow a predictable pattern: search_/get_ for entity lookups, find_ for exceptions, generate_ for reports. Minor deviations like search_reference_globally and long compound names are still clear.
23 tools is on the heavy side and above the typical well-scoped range. Most tools have a distinct purpose, but the many report/audit variants inflate the surface without adding entirely new capabilities.
The read-only audit domain is well covered: search/detail for products, lots, locations, moves, plus summaries, negative-balance checks, root-cause analysis, and reports. A few gaps remain, such as a general current-balance listing by lot/location and a way to enumerate all records without search filters.