Kani MCP Server

Overview Schema Source Related Servers Discussions Admin

list_assignments

Read-onlyIdempotent

Retrieve WaniKani assignments with filters for subject type, level, SRS stage, review or lesson availability, and progress status to target specific items.

Instructions

List assignments with optional subject, level, SRS, and availability filters

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_assignments"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	No
`burned`	No
`hidden`	No
`levels`	No
`passed`	No
`started`	No
`unlocked`	No
`srs_stages`	No
`subject_ids`	No
`page_after_id`	No
`subject_types`	No
`updated_after`	No
`page_before_id`	No
`available_after`	No
`available_before`	No
`immediately_available_for_review`	No
`immediately_available_for_lessons`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Oct 23, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered. The description adds nothing behavioral beyond that — it doesn't mention that results are paginated (despite page_after_id/page_before_id in the schema), what the default ordering or page size is, or what happens when no filters are supplied.

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 front-loaded sentence with no filler and no redundancy. Its brevity is appropriate in form, though the space saved was spent on nothing rather than on the missing parameter detail.

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?

A zero-required-parameter, 17-field query tool with no output schema and no field descriptions demands far more than one sentence. An agent cannot know from this description how to page through results or what the boolean flags (burned, passed, started, unlocked, hidden) select.

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% across 17 parameters, so the description carries the full burden — yet it only gestures at four filter families (subject, level, SRS, availability). Undocumented elsewhere: ids, burned, hidden, passed, started, unlocked, subject_types, updated_after, and both pagination cursors.

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 (List) and resource (assignments) plus the filter dimensions it supports, so the agent knows exactly what it returns a collection of. It doesn't distinguish itself from siblings like list_subjects or list_reviews, which is the only gap at this level.

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?

The word 'optional' tells the agent it can call with no arguments, but there is no guidance on when to prefer this over list_subjects, list_reviews, or list_level_progressions, and no mention of pagination expectations or result limits. Usage must be inferred entirely from the name.

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

Deploy Server