K2 Study Decks & Algorithm

search_deck

Read-only

Search one deck. query substring-matches the term, its reading/pronunciation, its English meanings, and its category, so "bone" finds entries glossed as bone and "ㄱ" finds that jamo. Narrow with category (exact, from list_decks) or difficulty (1-5; for the kanji deck this is the school grade). Paginated via offset.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "deck": "<deck>"
    },
    "name": "search_deck"
  }
}

Input Schema

Name	Required	Description
`deck`	Yes	Deck id from list_decks
`limit`	No	Max results (default 20, max 50)
`query`	No	Substring to match against term, reading, meanings, category
`offset`	No	Skip this many matches (paging)
`category`	No	Exact category filter (see list_decks)
`difficulty`	No	Exact difficulty/grade filter (1-5; kanji deck = grade 1-6)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / deck / enum

Previous value: -[
-  "japanese-kanji",
-  "japanese-vocabulary",
-  "chinese",
-  "hangul",
-  "spanish",
-  "french",
-  "latin",
-  "medica"
-]New value: +[
+  "japanese-kanji",
+  "japanese-vocabulary",
+  "chinese",
+  "hangul",
+  "spanish",
+  "french",
+  "latin",
+  "medica",
+  "nature-birds"
+]

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The readOnly annotation already establishes safe read behavior, and the description adds useful matching semantics: substring matching across term, reading, meanings, and category. It also explains exactness for `category` and the kanji-deck interpretation of `difficulty`.

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 short, front-loaded, and every sentence serves a purpose. Examples are compact and directly clarify query matching without adding filler.

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

Completeness5/5

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

For a six-parameter search tool with full schema coverage and read-only annotations, the description covers the critical behavior: what is searched, how to filter, and how to paginate. No output schema exists, so return-value detail is not required here.

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 100%, so the schema already documents all six parameters. The description reinforces query behavior and adds examples such as "bone" and "ㄱ", but most of its parameter information is already present in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: search one deck. It distinguishes the operation from deck listing and entry retrieval by focusing on query-based filtering within a deck.

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?

It gives clear operational guidance for narrowing results with `category` or `difficulty` and for paging with `offset`. It does not explicitly say when to use `get_entry` or `list_decks` instead, but the search context is clear.

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

All K2 Study Decks & Algorithm 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?