Skip to main content
Glama

mnemon_query_advisor

Inspects slow query execution plans per tenant, delivering automated FinOps index recommendations and circuit breaker health insight to help diagnose and tune database performance.

Instructions

Inspect slow query execution plans, automated FinOps index recommendations, and circuit breaker health.

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": {
      "tenant_id": "<tenant_id>"
    },
    "name": "mnemon_query_advisor"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenant_idYesDatabase tenant identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Inspect' implies a read-oriented operation, but the description does not explicitly confirm read-only behavior, mention side effects, permissions, rate limits, or whether recommendations are merely advisory.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no wasted wording. It efficiently lists the three inspection areas, though the phrasing is somewhat list-like rather than explanatory.

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?

The description identifies the three areas the tool inspects, which partially compensates for the absence of an output schema. However, it lacks usage routing and explicit behavioral context, leaving meaningful gaps for an agent choosing among the many sibling tools.

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?

There is only one parameter, tenant_id, and the input schema already documents it at 100% coverage. The description adds no additional parameter meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 states a specific inspection verb and names three concrete resources: slow query execution plans, FinOps index recommendations, and circuit breaker health. It is clear enough to understand the tool's scope, though it does not distinguish itself from sibling tools such as mnemon_get_slow_queries.

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

Usage Guidelines2/5

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

The description lists what can be inspected but gives no explicit guidance on when to use this tool versus alternatives like mnemon_get_slow_queries or mnemon_admin_kill_query. There are no exclusions, prerequisites, or routing cues.

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