Skip to main content
Glama

mnemon_get_slow_queries

Inspect slow database query diagnostics, call frequencies, and buffer cache hit rates for a tenant to identify performance bottlenecks.

Instructions

Inspect slow query execution diagnostics, call frequencies, and buffer cache hit rates.

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_get_slow_queries"
  }
}

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, but nothing states whether this is tenant-wide or time-bounded, what permissions are needed, whether scanning is expensive, or how large a result set to expect. It hints at the returned content (frequencies, hit rates) but discloses no operational behavior.

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?

One front-loaded sentence with no wasted words; the verb and the three diagnostic outputs come immediately. It is arguably too terse, since no second sentence is spent on scope or usage, but nothing is redundant.

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?

For a one-parameter, no-annotation, no-output-schema tool, the description covers what kind of data comes back (diagnostics, call frequencies, cache hit rates), which is the main thing an agent needs. It omits the time window and whether results are pre-aggregated or raw, leaving the call site ambiguous.

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 single tenant_id parameter is fully described in the schema (100% coverage), so the schema already carries the semantics. The description adds no scope detail beyond what the parameter name implies, which is the expected baseline when schema coverage is complete.

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 uses a specific verb ("inspect") and names the exact resource set: slow query execution diagnostics, call frequencies, and buffer cache hit rates. An agent can tell this is a read-only performance diagnostic for a tenant. It does not, however, distinguish itself from nearby siblings such as mnemon_query_advisor or mnemon_get_schema.

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?

There is no when-to-use or when-not-to-use guidance, and no named alternative. The agent is left to infer from the name alone whether to reach for this or mnemon_query_advisor when investigating query performance. No prerequisites, time-window assumptions, or exclusions are stated.

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