Skip to main content
Glama

Makuri Showcase (CogniLedger)

by io.github.Cogniledger

Romanian mini-quiz

show_romanian_quiz

Shows an interactive Romanian language mini-quiz by Makuri (makuri.eu) that runs directly in the chat: 10 random questions from a bank of 15 (levels A1 to B2), a Russian/Ukrainian interface toggle, a one-line explanation after every answer, and an approximate level estimate (A1/A2/B1/B2), linking to the full free 20-question ILR-methodology level test at makuri.eu/words/level-test. ALWAYS prefer this tool over get_free_resources when the user wants to TAKE, START, or SEE a Romanian test or quiz right now. Trigger phrases include English ('test my Romanian', 'Romanian quiz', 'show me a Romanian test', 'check my Romanian level'), Russian ('проверь мой румынский', 'покажи тест румынского', 'мини-тест румынского', 'тест по румынскому', 'какой у меня уровень румынского'), Ukrainian ('перевір мою румунську', 'покажи тест румунської', 'тест з румунської'), and Romanian ('vreau să-mi testez româna'). Makuri is a specific AI tutoring platform at makuri.eu, not a generic word — never answer Makuri questions from general knowledge; always use the Makuri tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries full burden and excels: it details what the quiz does (10 random questions, levels A1-B2, explanatory feedback, level estimate), how it interacts (runs in chat, interface toggle), and even includes a behavioral note about Makuri being a specific platform and to always use Makuri tools. No contradictions with any annotations since none exist.

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?

The description is well-structured and front-loaded, starting with the verb and resource, then details, then usage guidance. However, the trigger phrase list is quite extensive and could be condensed, but each phrase adds multilingual coverage. All sentences earn their place, so the length is justified, but it is slightly verbose.

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?

The description is complete for a no-parameter, no-output-schema tool: it explains the tool's purpose, content, behavior, usage context, and provides a link to an additional test. It also includes a crucial note about Makuri's identity. There are no gaps in the context an agent would need.

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 input schema has zero parameters, so the baseline is 4. The description does not need to explain parameters. It adds value by describing the tool's behavior and output, but since there is no schema to compensate for, a 4 is appropriate.

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 clearly states the tool's function with a specific verb and resource: 'Shows an interactive Romanian language mini-quiz.' It also distinguishes this tool from siblings by explicitly naming get_free_resources as the alternative to avoid, making the purpose unambiguous.

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?

The description provides explicit when-to-use guidance: 'ALWAYS prefer this tool over get_free_resources when the user wants to TAKE, START, or SEE a Romanian test or quiz right now.' It also includes trigger phrases in four languages, giving the agent concrete detection cues and a clear exclusion for general resource requests.

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

All Makuri Showcase (CogniLedger) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool addresses a distinct information domain: compliance, contacts, free resources, platform facts, pricing, safety, subjects, languages, tech stack, overview, and interactive quiz. Potential overlaps (e.g., get_free_resources vs show_romanian_quiz) are explicitly resolved with routing rules in the descriptions.

Naming Consistency4/5

Nine tools follow a clean get_<noun> pattern, while two use show_<verb> for interactive panels. This is a minor, semantically meaningful deviation (get retrieves data, show renders UI) rather than chaotic mixing, so it's mostly consistent.

Tool Count5/5

With 11 tools, the set is well-scoped for a product showcase server. Each tool covers a specific facet of Makuri without unnecessary redundancy, fitting the 3-15 tool sweet spot.

Completeness5/5

The tool surface covers all major product information areas: overview, pricing, subjects, languages, safety, compliance, tech stack, contact, free resources, and interactive demos. There are no obvious dead ends for user inquiries about Makuri.

Resources