Skip to main content
Glama
Sign In
xamp

xamp

by yeyorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

write_query

Execute SQL write queries (INSERT, UPDATE, DELETE, DDL) on a specified database. Requires write permission enabled.

Instructions

Ejecuta una consulta SQL de escritura (INSERT, UPDATE, DELETE, DDL). Requiere MCP_XAMP_ALLOW_WRITE=true.

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": {
      "database": "<database>",
      "query": "<query>"
    },
    "name": "write_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
databaseYesNombre de la base de datos.
queryYesConsulta SQL de escritura.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Discloses the authorization requirement (MCP_XAMP_ALLOW_WRITE=true), which is useful behavioral context. However, with no annotations, it omits details like error handling, idempotency, or destructiveness.

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

Conciseness5/5

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

Single sentence covering purpose and requirement, no fluff. Front-loads critical information.

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?

With no output schema and a destructive tool, the description could mention return value (e.g., affected rows) or security warnings. It provides minimal but sufficient context for basic use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, providing baseline 3. Description adds value by specifying query types (INSERT, UPDATE, DELETE, DDL), reinforcing the write nature beyond the schema description.

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?

Clearly states it executes SQL write queries (INSERT, UPDATE, DELETE, DDL). Distinguishes from sibling read_query and metadata tools.

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

Usage Guidelines4/5

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

Implies usage for write operations by listing write command types and a required environment variable, but does not explicitly contrast with read_query or state when not to use.

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