Skip to main content
Glama

get_practice_pool

Obtain a set of Japanese words and grammar the learner has already mastered for active-use practice. Pick relevant items to build a themed conversation scenario.

Instructions

Get a pool of Japanese words and grammar the learner has ALREADY mastered, for active-use practice — the opposite of the review queue. Use this when the learner wants to be tested on or practice words they already know, not review what they're forgetting. Workflow: (1) ideate a concrete conversation theme or scenario (ordering at an izakaya, complaining about the weather, a job interview); (2) call this to get the mastered pool; (3) the pool is NOT pre-filtered by theme — from it, you pick the words and grammar that fit your theme, using each item's meaning; (4) propose the scenario and your chosen words to the learner and get their buy-in before starting; (5) run the practice conversation; (6) at the end, call submit_grades once for every item you practiced — grade fluent use 3 or 4, hesitation 2, and a blank or misuse 1 with a one-sentence error_note. Returns each item with its meaning and reading so you can select by theme.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoboth
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
poolYes
returnedYes
generated_atYes
total_masteredYes
Behavior4/5

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

Describes key behaviors: returns mastered items with meaning/reading, no pre-filtering by theme. No annotations exist, so description carries full burden. Could mention ordering or size constraints, but limit parameter addresses size. Good overall.

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?

Information-dense with essential workflow details. Slightly verbose in places (e.g., repeating contrast with review queue), but front-loaded with main purpose. Efficient overall.

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?

Covers pre-use, usage, and post-use steps, and references output schema by mentioning meaning/reading. Missing parameter explanations, but otherwise complete for a tool with output schema.

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

Parameters1/5

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

Schema coverage 0% and description does not explain the 'kind' parameter (enum of grammar/vocab/both) or 'limit'. Only workflow implies both word types, but no clarification. Fails to add meaning beyond 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?

Clearly states it returns mastered items for active practice, contrasting with review queue. Specific verb 'Get', resource 'pool of mastered words/grammar', and purpose 'active-use practice'. Distinguishes from sibling get_review_queue.

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

Usage Guidelines5/5

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

Explicitly says when to use ('when learner wants to be tested on known words, not review forgotten ones') and provides a full 6-step workflow including after-call actions like item selection and submit_grades. Also notes pool is not pre-filtered.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Muslinmin/Japanese_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server