oci-mcp-blueprint
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_schemaA | Return the fake, hard-coded sample database schema used by the OCI MCP Blueprint demo server. |
| get_dataA | Return simulated rows from the fake sample database using a small demo condition language. This tool never executes SQL. |
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: get_data returns simulated data, while get_schema returns the schema definition. No overlap or ambiguity.
Both tools follow a consistent verb_noun pattern (get_data, get_schema), making the naming predictable and clear.
With only 2 tools, the server is intentionally minimal as a demo blueprint. While the count is low, it aligns with the server's stated purpose of providing a simple, fake sample database demonstration.
The tool set covers the essential operations for a demo database: retrieving the schema and querying data. There are no obvious gaps given the server's limited scope, though it lacks more advanced query or management features.