mcp-onprem-starter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UPSTREAM_BASE_URL | No | Base URL of the upstream REST API. If unset, the server uses a bundled mock upstream. |
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 |
|---|---|
| list_recordsA | List records from the upstream system, optionally filtered by a search query. Returns a bounded page of results with a total-matched count and a truncated flag — call again with a narrower query if truncated is true rather than assuming this is the full set. Use get_record to fetch one record in full. |
| create_recordA | Create a new record in the upstream system. Defaults to a dry run: confirm=true is required to execute, while the default returns a preview of the exact payload that would be sent. Set confirm=true to execute — this also requires the deployment to have ALLOW_WRITES enabled, independent of this flag. |
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 2 tools
The two tools have clearly distinct purposes: list_records for querying/searching with pagination, and create_record for inserting new records. No overlap or ambiguity exists.
Both tools follow a consistent verb_noun pattern (list_records, create_record), making the API predictable and easy to navigate.
At 2 tools, the set is on the thin side, but for a 'starter' server it could be intentionally minimal. However, the reference to get_record suggests at least one more expected tool.
The set is missing get_record, update_record, and delete_record. list_records explicitly instructs agents to use get_record, but that tool does not exist, creating a clear dead end and significant coverage gap.