Skip to main content
Glama

Coline

List cards

alert_cards_list
Read-onlyIdempotent

Lists cards (one per thing going on at a connected tool) in places you can see. Filter by address, sender, state or level; needsMe lists the ones waiting on you.

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_cards_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNo
stateNoopen
needsMeNo
minLevelNo
senderIdNo
addressIdNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
cardsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/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 covered. The description adds genuine context beyond that — permission scoping ("places you can see") and result cardinality (one card per active item) — but says nothing about ordering, pagination behavior, or the default open-state filtering that a caller would want to know.

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?

Two dense sentences with zero filler; the definitional parenthetical is front-loaded before the filter inventory. Every clause carries information the agent would otherwise have to guess.

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

Completeness4/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 described, and the annotations cover the safety semantics. What remains thin is filter detail for a list tool with 8 parameters — `since` and `limit` go unmentioned and level direction is unstated — but the core contract is conveyed.

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 description coverage is only 13% (only `workspace` is documented), so the description must compensate. It does partially: address, sender, state and level map onto addressId, senderId, state and minLevel, and "needsMe lists the ones waiting on you" clarifies that flag's meaning. However it never explains `since` or `limit`, and leaves `minLevel`'s 1-4 scale direction (minimum level, but which level is most severe?) ambiguous.

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

Purpose4/5

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

Names a specific verb+resource ("Lists cards") and adds a parenthetical that defines what a card is ("one per thing going on at a connected tool"), which an agent could not infer from the name. It also scopes results to "places you can see," distinguishing it from a fetch-by-id sibling like alert_card_get, though it never names that sibling explicitly.

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

Usage Guidelines3/5

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

The description implies usage by enumerating available filters and calls out the needsMe shortcut, so an agent knows how to narrow results. But it never states when to prefer this over alert_events_list or alert_card_get, and offers no exclusions or prerequisites, leaving the alternative-selection decision to inference.

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