Skip to main content
Glama
happypod-mcp

happypod-mcp

Official
by happy-pod

Database connection

get_database_connection
Read-onlyIdempotent

Retrieve host, port, database, user, and masked connection URL for a managed database; optionally reveal the real URL for secret injection without exposing it.

Instructions

Host, port, database and user, plus the connection URL with the password masked. reveal: true returns the real URL: use it only to pass into set_env secrets, never print it to the user.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "databaseId": "<databaseId>"
    },
    "name": "get_database_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
revealNo
databaseIdYesDatabase id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world semantics, so the description is not obligated to explain safety of the call itself. It does add genuinely non-obvious behavior: the URL is returned with the password masked by default and unmasked under reveal, plus an operational constraint that the revealed secret must be routed to set_env rather than surfaced. It stops short of covering failure behavior for an invalid databaseId or any authorization requirements.

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

Conciseness5/5

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

Two sentences, zero filler: the first front-loads the returned fields, the second attaches the only dangerous parameter to its safe usage. Every clause carries either expected output or a safety rule, and the secret-handling instruction is placed where an agent will read it before calling.

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

Completeness4/5

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

With only two parameters, no nested objects, and no output schema, the description covers what an agent needs: what comes back, what the default masking means, and how to handle the revealed value. Missing is anything about error handling for a nonexistent or unauthorized databaseId, a minor gap for a read-only tool whose annotations already signal safety.

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

Parameters4/5

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

Schema coverage is 50%: databaseId has a one-line description, and reveal has none. The description compensates precisely where the schema is silent, explaining that reveal=true returns the real URL while the default masks the password — the single most consequential semantic in the tool. The databaseId parameter still receives no added meaning beyond 'Database id'.

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 enumerates exactly what the call returns — host, port, database, user, and a masked connection URL — which makes the resource unambiguous and easily separable from siblings like list_databases or get_deployment. It lacks an explicit verb ('retrieve/get'), so the purpose is conveyed by the return payload rather than a stated action, which keeps it just short of a 5.

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

Usage Guidelines4/5

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

It gives a concrete, actionable rule for the risky path: 'reveal: true ... use it only to pass into set_env secrets, never print it to the user,' naming the sibling it should feed. It does not state when to prefer this tool over other database-related siblings or what preconditions (e.g. database existence, permissions) apply, so there is no explicit when-not guidance beyond the reveal constraint.

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