Skip to main content
Glama

Coline

List rules

alert_rules_list
Read-onlyIdempotent

Rules in plain words for a place, a sender, or your own.

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>"
    },
    "name": "alert_rules_list"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
rulesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds nothing beyond that — no note on pagination, result ordering, or what happens when multiple filters are combined, and no clarification of whether workspace scoping is mandatory.

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

Conciseness3/5

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

It is a single short sentence with no filler, so nothing is wasteful. However, the brevity comes at the cost of substance — the space saved is not reallocated to the scope or filter detail the agent needs.

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?

An output schema exists, so return values need not be explained. But with four parameters at 25% description coverage and a non-trivial scoping decision (workspace required plus three optional filters), the description leaves too much for the agent to guess.

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 only 25%, so the description must carry the filter semantics, yet it maps only loosely: "a place" plausibly corresponds to addressId, "a sender" to senderId, and "your own" to mine, but the mapping is never made explicit. The required workspace parameter is not mentioned at all, and no guidance is given on combining or precedence of filters.

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

Purpose2/5

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

"Rules in plain words for a place, a sender, or your own" names the resource but supplies no verb and reads more like a tagline than a statement of what the tool does. "In plain words" is ambiguous — it could describe natural-language rule text or a simplified output format, and an agent cannot resolve which from the text alone.

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 when-to-use guidance is given, and no sibling is named as an alternative (e.g., alert_rule_add for creating a rule). The three scope phrases weakly imply the tool is for looking up existing rules, but the agent must infer even that.

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