Skip to main content
Glama
Sign In
infra-mcp

infra-mcp

by esp4ce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_db_status

Diagnose database issues by retrieving connection counts, waiting locks, and long-running queries.

Instructions

Returns health metrics for a configured database: connection counts, waiting locks, and long-running query count.

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": {
      "db": "<db>"
    },
    "name": "get_db_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
dbYesDatabase name as defined in infra-mcp.yaml

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / db / description
      Added value: +"Database name as defined in infra-mcp.yaml"
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It describes the output but does not mention side effects, permissions required, caching, or rate limits. It is adequate but thin for a read-only tool.

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?

The description is a single concise sentence that front-loads key information. Every word adds value, and there is no redundancy or verbosity.

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?

Given the tool has one parameter and an output schema, the description provides sufficient context on what the tool returns (three health metrics). It could mention permissions or prerequisites, but overall it is complete enough for a simple tool.

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 already covers the 'db' parameter with a clear description ('Database name as defined in infra-mcp.yaml'). The description adds no additional meaning beyond implying the parameter specifies which database.

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 states the tool returns health metrics for a configured database, listing specific metrics (connection counts, waiting locks, long-running query count). This is specific and distinguishable from sibling tools like get_service_status or get_infra_overview.

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 implies usage for checking database health, but does not explicitly state when to use this tool versus alternatives. No when-not or alternative guidance is provided, leaving room for ambiguity.

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

Deploy Server

Other Tools