maximo-jobplan
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAXIMO_API_KEY | Yes | Your Maximo API key | |
| MAXIMO_BASE_URL | Yes | Your Maximo instance URL, e.g., https://your-maximo-instance.com |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| import_jobplansB | Import job plans from CSV data into Maximo. CSV must have columns: JPNUM,DESCRIPTION,JPDURATION,STATUS,JOBTYPE,PLUSCJPREVNUM |
| list_jobplansB | List job plans from Maximo with optional filtering |
| get_jobplanB | Get details of a specific job plan by number |
| delete_jobplanB | Delete a job plan by number |
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 4 tools
Each tool targets a distinct operation: delete, retrieve single, bulk import, and list. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with underscores (delete_jobplan, get_jobplan, import_jobplans, list_jobplans).
With 4 tools covering basic CRUD and listing, the count is well-scoped for a job plan management server.
The set covers create (via import), read, list, and delete, but lacks a dedicated update tool. Import may handle updates, but this is not explicit.