Skip to main content
Glama

alerts_update

Update an existing SQL alert by specifying its ID, name, query ID, and trigger condition. Modify notify settings, schedule, and other optional parameters.

Instructions

Update an existing SQL alert.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAlert ID
nameYesAlert name
query_idYesID of the saved query to evaluate
conditionYesTrigger condition: {'op': '>' | '<' | '>=' | '<=' | '==' | '!=', 'operand', 'threshold'}
notifyNoNotify settings: {'subscribers': [...]}
optionsNo
rearmNo
scheduleNo
parentNo
evaluationNo
run_as_roleNoOWNER | VIEWER
custom_subjectNo
custom_bodyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Annotations only indicate readOnlyHint:false, which matches the 'Update' verb, but the description provides no additional behavioral details such as partial update support, error behavior, 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.

Conciseness2/5

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

The single-sentence description is too brief for a tool with many complex parameters and nested objects. It sacrifices necessary detail for brevity.

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

Completeness1/5

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

With 13 parameters, 4 required, nested objects, and an output schema, the description provides almost no context about usage, return values, or parameter semantics, leaving the agent underinformed.

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

Parameters2/5

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

Schema description coverage is low (46%), yet the description adds no parameter information beyond what the schema already provides. For a tool with 13 parameters, more context is needed.

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 action ('Update') and the resource ('an existing SQL alert'), distinguishing it from sibling tools like alerts_create or alerts_delete.

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 guidance on when to use this tool vs alternatives. It doesn't mention that alerts_create should be used for new alerts, or any prerequisites like alert existence.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/inav/databricks-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server