Skip to main content
Glama

mnemon_configure_scaling

Configure Aurora Serverless v2 or Neon ACU scaling limits per tenant—set min/max ACU and idle timeout to control database capacity and scale-to-zero behavior.

Instructions

Configure Aurora Serverless v2 / Neon ACU scaling limits (min ACU, max ACU, scale-to-zero timeout).

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

Input Schema

NameRequiredDescriptionDefault
max_acuNoMaximum ACU capacity (e.g. 16.0 or 128.0)
min_acuNoMinimum ACU capacity (e.g. 0.0 for scale-to-zero)
tenant_idYesDatabase tenant identifier
idle_timeout_secNoInactivity seconds before scaling to zero (default: 300)

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 supplied, so the description carries the full behavioral burden and does not meet it: it never says whether changes apply immediately or take effect on next scale cycle, whether lowering max ACU can disrupt active queries, what permissions are required, or whether the operation is reversible. Only the existence of a scale-to-zero timeout concept is conveyed, which is already 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.

Conciseness4/5

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

A single front-loaded sentence with the verb and resource first and supporting detail in parentheses — no filler or hedging. The parenthetical partially duplicates fields the schema already documents, which is the only slight redundancy.

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 four-parameter mutation tool with no annotations and no output schema, the definition identifies the operation and its knobs but omits effect semantics, failure/rollback behavior, and what a successful call returns or confirms. Adequate to attempt a call, but thin for a capacity-changing mutation.

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?

Schema description coverage is 100%, so the schema already explains min_acu, max_acu, idle_timeout_sec and the default of 300 seconds, establishing a baseline of 3. The description's parenthetical adds little beyond naming the same three concepts and does not clarify, for example, ACU units or valid ranges/dependencies between min and max.

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?

States a specific verb+resource: 'Configure Aurora Serverless v2 / Neon ACU scaling limits', with the configurable dimensions listed in parentheses, so an agent immediately knows this mutates capacity settings rather than reading them. It does not distinguish itself from the sibling thanaton_configure_scaling, which appears to be the same operation for a different target, leaving the choice ambiguous.

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 explicit when-to-use or when-not-to-use guidance, no prerequisites (e.g. that a tenant must already exist), and no routing to the sibling scaling tool or to pooler configuration. Usage is only implied by the tool name and the ACU vocabulary.

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