w5-pg-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_MODEL | No | Model to use | gpt-5.2-mini |
| CACHE_ENABLED | No | Enable schema caching | true |
| DATABASE_HOST | No | PostgreSQL host | localhost |
| DATABASE_NAME | Yes | Database name (required) | |
| DATABASE_PORT | No | PostgreSQL port | 5432 |
| DATABASE_USER | Yes | Database user (required) | |
| CACHE_MAX_SIZE | No | Maximum number of schemas to cache | 100 |
| OPENAI_API_KEY | Yes | OpenAI API key (required) | |
| OPENAI_TIMEOUT | No | OpenAI API timeout in seconds | 30 |
| CACHE_SCHEMA_TTL | No | Schema cache TTL in seconds | 3600 |
| DATABASE_PASSWORD | Yes | Database password (required) | |
| OPENAI_MAX_TOKENS | No | Maximum tokens per request | 32000 |
| SECURITY_MAX_ROWS | No | Maximum rows per query | 10000 |
| OPENAI_TEMPERATURE | No | Model temperature | 0.0 |
| DATABASE_MAX_POOL_SIZE | No | Maximum connection pool size | 20 |
| DATABASE_MIN_POOL_SIZE | No | Minimum connection pool size | 5 |
| RESILIENCE_MAX_RETRIES | No | Maximum retry attempts | 3 |
| RESILIENCE_RETRY_DELAY | No | Initial retry delay in seconds | 1.0 |
| OBSERVABILITY_LOG_LEVEL | No | Log level | INFO |
| DATABASE_COMMAND_TIMEOUT | No | Query timeout in seconds | 30 |
| OBSERVABILITY_LOG_FORMAT | No | Log format (json/text) | json |
| RESILIENCE_BACKOFF_FACTOR | No | Exponential backoff multiplier | 2.0 |
| OBSERVABILITY_METRICS_PORT | No | Metrics HTTP port | 9090 |
| SECURITY_BLOCKED_FUNCTIONS | No | Comma-separated list of blocked PostgreSQL functions | |
| SECURITY_MAX_EXECUTION_TIME | No | Query execution timeout in seconds | 30 |
| OBSERVABILITY_METRICS_ENABLED | No | Enable Prometheus metrics | true |
| SECURITY_ALLOW_WRITE_OPERATIONS | No | Allow INSERT/UPDATE/DELETE operations | false |
| RESILIENCE_CIRCUIT_BREAKER_TIMEOUT | No | Circuit breaker timeout in seconds | 60 |
| RESILIENCE_CIRCUIT_BREAKER_THRESHOLD | No | Number of failures before circuit breaker opens | 5 |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| addA | Add two numbers |
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 1 tool
With only one tool, there is no possibility of confusion or overlap. The purpose of 'add' is clearly stated as adding two numbers.
A single tool cannot exhibit naming inconsistency. The name 'add' is a simple, clear verb that matches its function.
A single trivial arithmetic operation is severely under-scoped for a server named 'w5-pg-mcp', which implies a database-related purpose. The tool count is far too low for any meaningful functionality.
The tool surface is severely incomplete. Even as a math utility, it lacks basic operations like subtract, multiply, or divide, and it bears no relation to the apparent 'pg' (Postgres) domain implied by the server name.