Skip to main content
Glama

ilias_card_preview

Read-only

Load the pending preview for a specific approval card by approval reference so users can review the item awaiting approval.

Instructions

Load the pending preview for this 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": {
      "approval_ref": "<approval_ref>"
    },
    "name": "ilias_card_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
approval_refYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.4

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only the word "pending," indicating the card is in an undecided state, and does not say whether loading a preview has any side effects (e.g., marking it as reviewed) or what the payload contains.

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

Conciseness4/5

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

A single short sentence with the action front-loaded and no filler. It is efficient, though its brevity comes at the cost of the substance scored elsewhere.

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?

With no output schema and no annotation-level detail about results, the definition never explains what a "preview" returns or how it relates to the approval decision flow. For a tool operating on a pending approval card, that is a material gap.

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 the single required parameter approval_ref, so the description must carry the burden and largely does not. "This approval card" gestures at the parameter's meaning but gives no format, source, or example of a valid reference.

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?

"Load the pending preview for this approval card" names an action and an object, but "preview" is undefined and the phrasing doesn't distinguish it from the sibling ilias_card_decide, which acts on the same card. An agent gets the general idea but not a precise picture of what is returned.

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 call this versus inspecting or deciding on the card, no prerequisite that a pending approval must exist, and no mention of the decision tool as the follow-up. The sentence is purely descriptive.

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