Skip to main content
Glama

Coline

Add a rule

alert_rule_add

A rule in plain words, stored as written and given to the decision with every event: 'don't tell me about preview deploys', 'wake me if checkout breaks', 'ignore these until Monday'. personal: true makes it yours only.

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": {
      "workspace": "<workspace>",
      "text": "<text>"
    },
    "name": "alert_rule_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
personalNo
senderIdNo
addressIdNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
ruleYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent, closed-world write, so the bar is lower. The description still adds genuinely non-structured context: the text is stored verbatim and handed to the decision engine with every event, which tells an agent the string is interpreted later rather than parsed now. It does not mention duplicate handling or what happens to the text at evaluation boundaries.

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?

One compact sentence, front-loaded with the core concept and then the personal flag, with the quoted examples earning their space by making the expected free-text style concrete. Slightly dense but no filler.

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 an output schema present, return values need no explanation, and the behavioral essence of the text field is covered. However, for a mutation tool with two undocumented linkage parameters, the description should say how senderId/addressId and workspace scope the new rule, and whether repeated adds create duplicates.

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 only 20% (only workspace is documented), so the description must compensate, and it does explain the two most important fields: what 'text' should contain and the scoping effect of 'personal'. It says nothing about senderId or addressId, leaving two linkage parameters undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explains what a rule is conceptually and gives vivid examples of the natural-language text, but never states the action itself ('adds/creates a rule in this workspace') or its effect. It also does not differentiate from the sibling alert_rules_list, so the agent must infer the verb from the name and title.

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?

There is no when-to-use guidance, no mention of prerequisites or alternatives such as listing existing rules first via alert_rules_list, and no note on when to choose a personal rule versus a shared one beyond the bare 'personal: true makes it yours only'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources