JobBOSS2 MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JOBBOSS2_BASE_URL | No | JobBOSS² API origin | ECI production API |
| JOBBOSS2_CLIENT_ID | No | Integration Engine API user client ID | |
| JOBBOSS2_TOKEN_URL | No | OAuth token URL | ECI production token endpoint |
| JOBBOSS2_ACCESS_TOKEN | No | Static bearer token alternative | |
| JOBBOSS2_ALLOW_WRITES | No | Enable POST and PATCH tools | false |
| JOBBOSS2_CLIENT_SECRET | No | Integration Engine API user client secret | |
| JOBBOSS2_REQUEST_TIMEOUT_MS | No | Per-request timeout from 100 to 300000 ms | 30000 |
| JOBBOSS2_ENABLE_UNDOCUMENTED | No | Register the underspecified operation tool | 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jobboss2_describe_resourceA | List JobBOSS2 resources or inspect one resource's paths, keys, query parameters, and request schema. Call this before create or update tools. |
| jobboss2_listA | List a JobBOSS2 resource with documented fields, filters, sorting, and offset paging. Filter keys use field[operator], where operator is eq, ne, gte, lte, gt, lt, in, notin, or null. |
| jobboss2_getA | Get one JobBOSS2 record. Use jobboss2_describe_resource to find the exact key names required by the resource. |
| jobboss2_createA | Create a JobBOSS2 record. Request data is checked against ECI's OpenAPI schema. Use jobboss2_describe_resource first to inspect required parent keys and fields. |
| jobboss2_updateA | Patch a JobBOSS2 record. Request data is checked against ECI's OpenAPI schema. Use jobboss2_describe_resource first to inspect key names and writable fields. |
| jobboss2_issuing_materials_lookupA | List issuing-material bin locations, job numbers, or routing steps with standard JobBOSS2 filters and paging. |
| jobboss2_transfer_stock_to_jobA | Transfer stock material to a job. This changes bin quantities and can create job materials, inventory transactions, and job requirements. It is not safe to retry blindly. |
| jobboss2_create_reportB | Submit a JobBOSS2 report request. ECI's current OpenAPI document does not define this request body's fields or response schema. |
| jobboss2_get_reportA | Get a previously submitted JobBOSS2 report by request ID. ECI's current OpenAPI document does not define the response schema. |
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 9 tools
The generic resource tools (describe/list/get/create/update) and the report-specific tools are mostly distinct, and the two domain operations are clearly unique. Some ambiguity exists between generic create/get and create_report/get_report, but the descriptions clarify the report tools are for submitted report requests.
All tools share the jobboss2_ prefix, but the suffix pattern is inconsistent: bare verbs (list, get, create, update), verb_noun (describe_resource, create_report, get_report), noun_lookup (issuing_materials_lookup), and a phrasal verb (transfer_stock_to_job). This is readable but not a predictable verb_noun convention.
Nine tools is a reasonable size for a JobBOSS2 wrapper: generic CRUD, resource introspection, report submission/retrieval, and two domain-specific stock actions. Each tool addresses a distinct operation without excessive fragmentation.
The generic surface covers describe/list/get/create/update but omits delete, which is a notable gap for full lifecycle coverage. Report tools support submit and retrieve but no listing or cancellation, and the report schema is explicitly undefined, leaving agents with potential dead ends.