Skip to main content
Glama
JimmyAlter

guarded-sql-mcp

by JimmyAlter

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DATABASE_URLYesPostgreSQL connection URL, e.g. postgres://mcp_readonly:mcp_readonly_dev@localhost:5432/inventory. Always connect as mcp_readonly, never as the owner.
STATEMENT_TIMEOUT_MSNoPer-statement timeout inside each transaction, in milliseconds.5000

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_sitesA

List all sites with their code, city and number of non-retired devices.

search_devicesA

Search devices by site, status and operating system. Returns hostname, site, OS, status, IP and last check-in time.

get_deviceA

Get one device by hostname, including its site and the name and email of the person it is assigned to.

find_peopleA

Find people whose name or email contains the given text. Returns name, email, department and site.

device_softwareA

List software installed on a device, optionally filtered by package name.

stale_devicesA

List non-retired devices that have not checked in for at least the given number of days (or never), oldest first.

open_ticketsA

List tickets that are not closed, highest priority first, optionally filtered by site and priority.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct resource or query need: sites, device search, single device, people search, software, stale devices, and open tickets. The only potential overlap between search_devices and stale_devices is resolved by stale_devices' unique time-since-check-in criterion.

Naming Consistency3/5

Four tools follow a clear verb_noun pattern (list_sites, search_devices, get_device, find_people), but device_software, stale_devices, and open_tickets are noun phrases with no leading verb. Snake_case is consistent, but the overall convention is mixed.

Tool Count5/5

Seven tools is well-scoped for a read-only IT asset and ticketing query server. Each tool addresses a distinct query dimension without redundancy or bloat.

Completeness4/5

The surface covers core read queries across sites, devices, people, software, and tickets, which is strong for a guarded SQL query server. Minor gaps include no ticket detail/closed-ticket query, no person detail beyond search, and no write operations.

Maintenance

ActivityMaintained
ResponsivenessNo issues