moat-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | No | PostgreSQL connection string for the database. If not provided, a development default is used. |
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 |
|---|---|
| queryA | Execute a SELECT-style query inside a read-only transaction on the Postgres business database. |
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 available, there is no possibility of confusion or overlap between tools. The single 'query' tool's purpose is clearly distinct by default.
The tool name 'query' is a simple, accurate verb. With no other tools to compare against, the naming is trivially consistent.
A single tool feels thin, even for a narrowly scoped query-only server. It borders on being under-scoped, though it could work for a very specific use case.
The server lacks schema discovery or metadata inspection tools, forcing agents to rely on prior knowledge of the database structure. This is a significant gap that could lead to failures when querying unfamiliar tables.