Skip to main content
Glama
Sign In
Kani MCP Server

Kani MCP Server

by Alexxanddr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_summary

Read-onlyIdempotent

Retrieves lesson and review availability for the next 24 hours from WaniKani, helping you plan study sessions.

Instructions

Get lesson and review availability for the next 24 hours

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already disclose readOnlyHint=true, openWorldHint=true, and idempotentHint=true. The description adds useful temporal scope and clarifies that the tool returns availability rather than detailed records, but it does not describe return format, freshness, or any rate/auth considerations.

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?

The description is a single front-loaded sentence with no redundant or wasted wording. It states the core action and scope immediately.

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?

For a zero-parameter, read-only summary tool with no output schema, the description adequately conveys the returned content area: lesson and review availability over the next 24 hours. It could be more complete by describing whether availability means slots, counts, or flags, but it is sufficient for invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there are no parameter semantics to explain. This meets the baseline of 4 for a zero-parameter tool.

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 ('Get'), resource ('lesson and review availability'), and temporal scope ('next 24 hours'). It is clear what the tool does, though it does not explicitly distinguish itself from the many sibling list/get tools.

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 24-hour scope implies when this tool is useful, but the description gives no explicit when-to-use guidance, exclusions, or alternatives such as list_reviews or list_assignments. Usage is therefore inferred rather than stated.

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

Deploy Server

Other Tools