Skip to main content
Glama
Sign In
DuckPond MCP Server

DuckPond MCP Server

by jordanburke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

execute

Execute SQL DDL/DML statements for a specific user without returning results. Use for managing per-user databases in a multi-tenant DuckDB setup.

Instructions

Execute SQL statement (DDL/DML) for a specific user without returning results

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": {
      "sql": "<sql>"
    },
    "name": "execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdNoUser identifier (optional if DUCKPOND_DEFAULT_USER is set)
sqlYesSQL statement to execute (DDL/DML)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.4.4

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only mentions that no results are returned, but crucially omits that executing DDL/DML can be destructive, requires certain permissions, may affect database state, and does not indicate error handling or side effects. This lack of transparency is a significant gap for a mutation tool.

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 sentence that efficiently conveys the core purpose and a key constraint (no results). It is front-loaded and without wasted words. However, it could be slightly restructured or bulleted for clarity, but overall it is concise and effective.

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?

Given the absence of output schema and annotations, the description should provide more contextual completeness. It fails to mention return value on success (e.g., affected rows), error behavior, prerequisites (e.g., user attachment), or whether the operation is idempotent. For a potentially destructive SQL execution tool, this is insufficient.

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 documents both parameters adequately. The tool description adds minimal value beyond what's in the schema—it reiterates that the SQL is DDL/DML and that userId is per user. This meets the baseline for high schema coverage but does not exceed it.

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 verb 'Execute', the resource 'SQL statement (DDL/DML)', the scope 'for a specific user', and the outcome 'without returning results'. This effectively distinguishes it from sibling tools like 'query' which likely return results, and from administrative tools like 'detachUser' or 'listUsers'.

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 provides no guidance on when to use this tool versus its siblings, especially 'query'. It does not mention that 'execute' is for DDL/DML operations without result sets, while 'query' is for SELECT statements that return results. There are no when-not-to-use instructions or alternatives listed.

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