O2C Deployment Workbench MCP Server
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 |
|---|---|
| get_implementation_summaryA | Return controlled benchmark KPIs, data-quality status, disclaimers, and agent readiness. |
| investigate_paymentC | Return matching evidence and exception routing for one synthetic payment. |
| get_collection_priorityA | Return the configured collection score evidence for one synthetic invoice. |
| run_controlled_benchmarkA | Regenerate synthetic source exports and controlled benchmark outputs; never connects to a genuine ERP. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| investigate_cash_exception | |
| assess_go_live |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| configuration_resource | |
| benchmark_resource | |
| observability_resource |
TDQS
Scored across 4 tools
Each tool targets a clearly distinct function: summary/KPIs, payment investigation, collection priority, and benchmark regeneration. There is no meaningful overlap or ambiguity between them.
All names use lowercase snake_case and follow a verb_object pattern, but the verb set is mixed (get, investigate, run). This is still predictable and readable, with only minor stylistic variance.
Four tools is a tight, well-scoped surface for a synthetic O2C benchmark workbench. Each tool serves a distinct purpose without unnecessary bloat or missing core functionality.
The tool set covers the main workflows: viewing benchmark status, investigating a payment, checking collection priority, and regenerating outputs. A minor gap is the lack of explicit discovery tools for available synthetic payment or invoice identifiers, but this may be addressed through the summary.