Update an existing query snippet in Redash by specifying its ID and modifying trigger, description, or SQL content.
Update an existing query snippet
| Name | Required | Description | Default |
|---|---|---|---|
| snippetId | Yes | ID of the snippet to update | |
| trigger | No | Trigger keyword for the snippet | |
| description | No | Description of the snippet | |
| snippet | No | The SQL snippet content |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, and the description only repeats 'update' without disclosing any behavioral traits such as required permissions, idempotency, or side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence, but it could be structured to include key details like required fields or expected outcomes.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with no annotations and no output schema, the description fails to provide sufficient context about return values, required fields, or behavioral effects.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for all four parameters, so the description adds no additional meaning beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Update an existing query snippet', specifying the verb and resource, and distinguishes it from siblings like create, delete, and get.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives, no prerequisites or when-not-to-use conditions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/suthio/redash-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server