Skip to main content
Glama

ilias_card_decide

Destructive

Approve or decline a pending ILIAS approval card by providing its token and decision, so users can resolve course approval requests.

Instructions

Respond to a single pending ILIAS approval card.

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": {
      "token": "<token>",
      "decision": "<decision>"
    },
    "name": "ilias_card_decide"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
decisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.4

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the risky profile is documented structurally. The description adds nothing beyond that — no statement that the decision is irreversible, that the card is removed from the pending queue, or whether approval can be undone. For a destructive, non-idempotent action this is a substantial gap.

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?

A single front-loaded sentence with no wasted words, which is structurally sound. However, its brevity reflects under-specification rather than economy, so it does not fully earn a high score.

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?

This is a destructive, non-idempotent mutation with no output schema and no parameter documentation. An agent needs to know token provenance and the consequence of each decision; neither is present, leaving the definition inadequate for the tool's complexity.

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 0% for two required parameters, so the description must compensate and does not. It never explains where the token comes from (presumably another tool's output) or that "decision" means approve versus decline and what each does.

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?

"Respond to a single pending ILIAS approval card" gives a verb and a resource with clear scope (one pending card), but "respond" is vague about what the response actually is — the approve/decline choice only surfaces in the schema enum, not the description. It is distinguishable from the list/scan siblings but not meaningfully from ilias_card_preview.

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 (e.g. obtaining a card token, previewing the card first), and no reference to alternatives such as ilias_card_preview. The agent must infer the workflow entirely.

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