Skip to main content
Glama
iflow-mcp

SentryFrogg MCP Server

by iflow-mcp

mcp_psql_manager

Manage PostgreSQL databases through encrypted credential profiles. Execute queries, explore schemas, and manipulate data with tools like quick_query, show_tables, and insert_data.

Instructions

PostgreSQL toolchain. Flow: setup_profile → action. setup_profile accepts credentials or connection_url plus optional TLS (ssl_mode, ssl_ca, ssl_cert, ssl_key, ssl_passphrase, ssl_servername, ssl_reject_unauthorized); secrets stored encrypted. Subsequent calls reuse profile_name: quick_query (adds LIMIT 100 if absent; supports params array for $ placeholders), show_tables, describe_table, sample_data, database_info, insert_data, update_data, delete_data, list_profiles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
profile_nameNoProfile name (defaults to 'default')
connection_urlNopostgres://user:pass@host:port/db url
hostNo
portNo
usernameNo
passwordNo
databaseNo
sslNo
ssl_modeNodisable | require | verify-ca | verify-full
ssl_caNoPEM encoded certificate authority chain
ssl_certNoPEM encoded client certificate
ssl_keyNoPEM encoded client private key
ssl_passphraseNoOptional passphrase for the private key
ssl_servernameNoOverride servername for TLS verification
ssl_reject_unauthorizedNoSet to false to trust self-signed certificates
sqlNo
paramsNo
table_nameNo
dataNo
whereNo
limitNo
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must cover behavioral traits. It includes key details like secret encryption and the automatic LIMIT 100 addition in quick_query. However, it does not disclose the nature of mutating actions (insert, update, delete) as potentially destructive or reversible, nor does it mention error handling or concurrency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph that front-loads the key flow but then delves into setup_profile parameter details. It could be more structured (e.g., bullet points for actions) without being overly verbose. It is concise but at the cost of clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (22 parameters, many actions, no output schema), the description provides a reasonable overview including the flow and key behaviors. However, it lacks information on return values for each action and has gaps in parameter explanations, making it adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning beyond the input schema for some parameters, such as the params array for $ placeholders and the automatic LIMIT in quick_query. However, with only 41% schema description coverage, many parameters remain unexplained. The description partially compensates but not fully.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is a PostgreSQL toolchain and lists the specific actions available, distinguishing it from sibling tools (API client, SSH manager) by domain. The purpose is well-defined with a clear flow: setup_profile then action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the required flow (setup_profile first), which implies usage guidance, but does not explicitly state when not to use this tool or provide comparisons to alternatives. For example, it does not advise against using destructive actions without caution.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/iflow-mcp/SentryFrogg-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server