fastmcp-opengauss
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENGAUSS_HOST | Yes | The openGauss database host | |
| OPENGAUSS_PORT | Yes | The openGauss database port | |
| OPENGAUSS_USER | Yes | The openGauss database user | |
| OPENGAUSS_DBNAME | Yes | The openGauss database name | |
| OPENGAUSS_PASSWORD | Yes | The openGauss database password |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_queryC | Execute an SQL commands on the openGauss server. Args: query: SQL command |
| list_tables_in_current_schemaB | List table names in current schema on the openGauss server. |
| get_table_definitionD | Get table definition. |
| get_current_user_and_schemaB | Get current schema and current user. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ListSchemas | Get all schemas of the database. |
| ListTables | Get all table names in current schema, in qualified table names, of the form <schema_name>.<table_name>. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no ambiguity: execute_query runs SQL commands, get_current_user_and_schema retrieves metadata, get_table_definition provides table structure, and list_tables_in_current_schema enumerates tables. The descriptions clearly differentiate these functions, making misselection unlikely.
The tools follow a consistent verb_noun pattern (e.g., execute_query, get_table_definition) with all using snake_case. However, get_current_user_and_schema is slightly longer and combines two nouns, which is a minor deviation from the simpler patterns of the other tools, but overall naming remains highly readable and predictable.
With 4 tools, the count is appropriate for a database server focused on basic querying and metadata operations. It covers essential functions without being overly sparse or bloated, though it could be considered slightly thin if more advanced features were expected, but it's reasonable for the apparent scope.
The toolset covers core database operations like query execution and metadata retrieval, but there are notable gaps. For example, it lacks tools for creating or modifying tables, managing users, or handling transactions, which are common in database interfaces. This could limit agent workflows, but basic querying and inspection are supported.