uNotes

List my quizzes

list_my_quizzes

Read-onlyIdempotent

List the authenticated user's own quizzes on uNotes (quizzes for the courses where the user has uploaded documents), newest first. Use it for any question about the user's quizzes, such as "what quizzes do I have for CSI3131?": put the course code or quiz title in query. This is the tool for the user's quizzes; the document library search does not cover them.

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

Input Schema

Name	Required	Description
`skip`	No
`limit`	No
`query`	No	Filter by quiz title, course code, or course name

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / skip / maximum
```
Added value: +9007199254740991
```
First observedOct 5, 2026

TDQS

A3.8/5.0

Behavior4/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 the safety profile is covered. The description adds genuinely new behavioral facts: the result set is restricted to the caller's own quizzes and returned newest-first. It omits return shape and pagination limits, but with full annotation coverage that is a modest gap.

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?

Three sentences, front-loaded with purpose, then usage, then disambiguation. Slight redundancy in the closing 'This is the tool for the user's quizzes' restating the opening, but nothing is wasted.

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?

For a paginated list tool with no output schema, the description should hint at what a quiz entry contains or how paging behaves. It covers routing and filtering well but leaves the return payload and pagination semantics entirely unstated.

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 coverage is only 33%, so the description must carry weight. It explains how to use 'query' ('put the course code or quiz title in query'), which usefully extends the schema's own wording, but says nothing about 'skip' and 'limit' or the 30-item cap. Partial compensation for the coverage gap.

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?

States a specific verb and resource ('List the authenticated user's own quizzes'), defines the scope (courses where the user uploaded documents) and ordering ('newest first'). It routes away from document-library search but never names the sibling 'list_quizzes', so the distinction between this and that near-identical tool is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit usage trigger ('Use it for any question about the user's quizzes') backed by a concrete example question, plus a when-not ('the document library search does not cover them'). No guidance on when to prefer list_quizzes or get_quiz over this tool, which keeps it short of a 5.

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

All uNotes tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?