itu-mcp

Overview Schema Source Related Servers Discussions Admin

Get Dashboard Assignments

get_dashboard_assignments

Read-onlyIdempotent

Retrieve assignments from the Ninova dashboard's aggregated assignments page, optionally including details or a list-only view for deadline checks.

Instructions

Return the assignments listed under the Ninova dashboard's aggregated assignments page. Set include_details=false for a faster list-only read.

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": "get_dashboard_assignments"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`include_details`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.2.1Oct 14, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties

Added value: +{
+  "result": {
+    "additionalProperties": true,
+    "title": "Result",
+    "type": "object"
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "result"
+]
```

changedOutput schema / title

Previous value: -"get_dashboard_assignmentsDictOutput"New value: +"get_dashboard_assignmentsOutput"

First observedv0.2.0Jul 10, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds a genuine behavioral tradeoff not present in the annotations: that include_details=false yields a faster, list-only read. It does not disclose pagination behavior, the meaning of the default 20-item limit, or whether results span all enrolled courses.

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

Conciseness5/5

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

Two sentences, zero filler, with the core purpose front-loaded and the performance tip following. Nothing in the text is redundant with the title or annotations.

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

Completeness4/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 described, and the safety profile is fully carried by annotations. The remaining gap is the undocumented limit parameter and the imprecise word "aggregated" (across courses? across terms?), which an agent may need to resolve to call this confidently.

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 description coverage is 0%, so the description carries the burden for both parameters. It explains the include_details tradeoff well but says nothing about limit, leaving half the parameters undocumented in both the schema and the description.

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 states a specific verb and resource ("Return the assignments listed under the Ninova dashboard's aggregated assignments page"), making it clear this is a dashboard-scoped assignment list. It does not, however, distinguish itself from closely named siblings such as get_course_assignments, get_upcoming_deadlines, or get_dashboard, leaving the agent to infer the boundary.

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?

The only guidance is a parameter-tuning hint ("Set include_details=false for a faster list-only read"), which is useful but is not a when-to-use rule. There is no statement of when this tool should be chosen over get_course_assignments or get_upcoming_deadlines, and no exclusions.

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

Deploy Server