GuardedServer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| --allow-adhoc | No | Optional CLI flag to add to the server arguments. When present, registers the ad-hoc `run_sql` tool, exposing one read statement. | false |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_queriesA | List the named, reviewed queries this warehouse offers, with what each answers. |
| describe_queryC | Parameters of one catalog query: name, type, whether required, allowed values. |
| run_queryA | Run a catalog query by name.
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| revenue_report | Ask for a one-page revenue summary of one region and year. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| schema | Every table and column in the warehouse, with types. |
| catalog | The full query catalog with parameter specs. |
TDQS
Scored across 3 tools
Each tool maps to a distinct step in a linear workflow: discover available queries (list_queries), inspect one query's contract (describe_query), and execute it (run_query). There is no overlap in purpose or resource targeting, so misselection is unlikely.
All three names follow a strict verb_noun snake_case pattern with a shared 'query' noun, and the verbs (list/describe/run) accurately signal the action. Highly predictable for an agent.
Three tools is the minimal complete set for a catalog-style execution server, and each earns its place in the discover-inspect-run sequence. Nothing is padded or redundant.
The read-only query lifecycle (discover, describe parameters, execute) is fully covered, including parameter placement, date formats, and row limits in the description. Minor gaps: describe_query does not expose result column schemas or output shape, and there is no way to surface query-level errors or examples before running.