Skip to main content
Glama
jin38324

oci-documentation-mcp-server

by jin38324
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FASTMCP_LOG_LEVELNoLog level for the MCP server (e.g., ERROR, INFO, DEBUG)ERROR

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

CapabilityDetails
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

NameDescription
oci_search_documentationA

Search OCI documentation based on a search phrase.

Usage

This tool searches OCI documentation pages matching your search phrase. Use it to find relevant documentation urls about OCI Productswhen you don't have a specific URL.

Search Tips

  • Use specific product name/technical terms rather than general phrases

  • Include service names to narrow results (e.g., "OCI Object Storage bucket versioning" instead of just "versioning")

  • Use quotes for exact phrase matching (e.g., "Using Instance Configurations and Instance Pools")

oci_read_documentationA

Fetch an OCI documentation page url and return content partially as markdown.

Handling Long Documents

If the response indicates the document was truncated, you have several options:

  1. Continue Reading: Make another call with start_index set to retrieve the next portion of the document.

  2. Stop Early: If you've already found the specific information needed, you can stop reading

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one reads a specific documentation page, the other searches for relevant pages. There is no overlap or ambiguity between them.

Naming Consistency5/5

Both tools follow a consistent pattern: 'oci_' prefix + verb + '_documentation'. The naming is predictable and clear.

Tool Count3/5

With only 2 tools, the server feels minimal. While read and search cover essential documentation operations, a small tool count like this is borderline and could benefit from additional tools (e.g., list categories or browse).

Completeness3/5

The tools cover the core workflow of searching and reading documentation. However, there is no tool for browsing documentation structure or listing available sections, which might be needed for efficient navigation.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources