Skip to main content
Glama

mnemon_execute_sql

Execute raw SQL directly on a tenant database cluster or branch to run queries against isolated sandbox data. Use it to inspect or modify tenant data without leaving the agent workflow.

Instructions

Execute raw SQL query directly on a tenant database cluster or branch.

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

Input Schema

NameRequiredDescriptionDefault
queryYesSQL query statement to execute
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 supplied, so the description carries the full behavioral burden. 'Execute raw SQL' implies arbitrary DDL/DML and therefore possible destruction, yet the description says nothing about permissions, transaction semantics, statement limits, timeouts, or reversibility. For a raw-SQL mutation-capable tool this is a serious disclosure gap.

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 no filler or redundancy. It is efficient, though its brevity leaves the substantive gaps to the other dimensions rather than being a flaw of wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a high-risk raw-SQL execution tool with no annotations and no output schema, the description should explain what comes back (rows vs. affected count), safety constraints, and error behavior. None of that is present, so an agent cannot call it confidently.

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 coverage is 100% with only two parameters, both documented in the schema, so the baseline is 3. The phrase 'tenant database cluster or branch' adds a little meaning about what tenant_id can address, but no query syntax, format, or multi-statement expectations are given.

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?

Names a specific verb and resource: 'Execute raw SQL query' against 'a tenant database cluster or branch'. That is clear enough to distinguish it from schema/advisor siblings like mnemon_get_schema or mnemon_query_advisor, but the description never states that distinction explicitly.

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?

No when-to-use or when-not-to-use guidance. It does not say whether to prefer mnemon_query_advisor for analysis, nor when to target a branch versus the primary cluster, nor any precondition for running arbitrary SQL.

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