Skip to main content
Glama

ilias_list_news

Read-only

Retrieves news items from the ILIAS dashboard or a specified course page, so you can review announcements and course updates without navigating the platform.

Instructions

News items from the dashboard news page, or from a given course page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ilias_list_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/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=true, so the safety profile is covered. The description adds the useful behavioral context that news can come from either the dashboard or a course page, but says nothing about defaults, pagination, ordering, or what happens when target is invalid.

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?

One short sentence with no filler, and the key distinction between dashboard and course-page news is front-loaded. It is efficient, though the extreme brevity contributes to the gaps in parameter guidance.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one optional parameter) and an output schema exists, so return-value detail is unnecessary. The critical missing piece is how the nullable target argument maps to a course, which leaves the agent guessing for the only input that affects behavior.

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 'target' parameter, so the description must carry the burden. It only implies that target refers to a course page ('from a given course page') and that omitting it reads the dashboard, without specifying accepted formats (ID, URL, slug) or the default behavior explicitly.

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?

The description identifies the resource ('News items') and the two sources it can read from (dashboard news page vs. a course page). The verb is implicit rather than stated, but the retrieval intent is unambiguous and distinguishable from sibling listing tools like ilias_list_courses or ilias_list_items.

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?

It indicates two usage contexts (dashboard-wide or a specific course page), which implies the optional target parameter selects the course scope. However, it gives no explicit when-to-use/when-not guidance, no prerequisites, and no hint about how to choose a target value.

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