Skip to main content
Glama

Coline

Get a card

alert_card_get
Read-onlyIdempotent

A card with its timeline of events and how its level was decided.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
cardYes
timelineYes
decisionsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description contributes a little behavioral context by indicating the payload includes an event timeline and the level-decision rationale, which tells an agent what evidence is available. It says nothing about missing/not-found behavior or any access constraints.

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, but it is a fragment that leads with a noun phrase instead of the operation. Brevity here comes at the cost of front-loading the core action.

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 for a two-required-parameter getter the definition still omits what the tool actually does, how cardId is obtained, and how it relates to alert_cards_list. An agent could invoke it only by guessing from the name and schema.

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?

At 50% schema coverage, the description adds no meaning for either parameter, and it never mentions that the tool is keyed by cardId within a workspace. The undocumented cardId is only inferable from the name and title, leaving the description to do none of the compensating work.

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?

The description is a noun phrase ('A card with its timeline of events and how its level was decided') rather than a verb+resource statement, so it never says it fetches a card by ID. The mention of timeline and level rationale does add content beyond the name, so it is not pure tautology, but an agent must infer the action from the title and tool name.

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 or when-not-to-use guidance, and no routing to alternatives such as alert_cards_list for enumeration or alert_card_act for acting on a card. The only implied usage is that this returns a single card's detail.

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