Skip to main content
Glama

Coline

Act on a card

alert_card_act

Resolved, Not a problem, Quiet these (mutes the kind), Assign to me, Make a task, Look again (the crew member looks once more), Handled (clears it from Needs you), Reopen, or Open fix in Code.

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>",
      "cardId": "<cardId>",
      "action": "<action>"
    },
    "name": "alert_card_act"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
cardIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
cardYes
runIdYes
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare the tool is a non-read-only, non-destructive, non-idempotent mutation, so the description only needs to add state-change context. It does add value for 'quiet' (mutes the kind) and 'handled' (clears it from Needs you), but leaves the effect of resolved, assign_to_me, make_task and reopen unexplained, and never says whether actions are reversible.

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 short, but it arrives as a single comma-spliced fragment with no lead sentence establishing what the tool does. The parenthetical glosses are useful; the list form makes it hard to scan the nine options against the ten enum values.

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?

For a mutation tool with an output schema and three required parameters, the description should at least frame the operation and note that a card identifier is required. It omits how to obtain cardId, what the result of each action is, and whether any action is irreversible, leaving the agent to guess before triggering a state change.

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 33% and only workspace is documented, so the description must carry the action parameter, which it partly does by mapping user-facing labels to enum meanings. However, the mapping is one-to-one imprecise: the enum value 'opened' has no corresponding label in the list, and 'Open fix in Code' could be read as either 'opened' or 'open_fix', while cardId is never explained.

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 is a bare enumeration of action labels rather than a sentence, so the agent must infer that this tool applies one of those actions to an alert card. The label set does implicitly separate it from the read-only sibling alert_card_get, but the purpose is never stated as a verb+resource.

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 guidance on when to pick this tool versus alert_card_get or alert_cards_list, and no prerequisites such as where cardId comes from. A few actions carry inline hints (quiet mutes the kind, handled clears it from Needs you), but nothing says when to choose resolved vs not_a_problem vs handled.

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