MCP OpsBridge

db_execute_query

Execute read-only SQL SELECT queries against PostgreSQL with parameterized values for safe data retrieval.

Instructions

Execute a read-only SQL query against PostgreSQL

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": {
      "query": "<query>"
    },
    "name": "db_execute_query"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	SQL SELECT query. Write operations are blocked.
`params`	No	Parameterized query values

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 10, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It states read-only, which is a key safety trait, but doesn't mention result format, error handling, or blocking of non-SELECT statements (though that's in the schema).

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?

Single sentence, direct, no filler.

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?

The description is sufficient for a simple query tool: states purpose and read-only constraint. The schema covers parameters. No output schema needed as query results are implicit. Minor gaps like multiple statements or returning large datasets are not critical.

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 schema describes both parameters (query and params) with 100% coverage. The description adds no additional parameter semantics beyond 'read-only', so baseline 3.

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

Purpose5/5

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

The description clearly identifies the verb 'execute', the resource 'SQL query', and the scope 'read-only' against PostgreSQL, distinguishing it from write/schema sibling tools.

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?

The read-only scope implies it's for SELECT queries, and sibling tools cover writes, but no explicit alternatives are named. It gives clear context that this is for reads only.

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