chaoslimba-mcp-server

Get Mystery Items

cl_get_mystery_items

Read-only

Retrieve mystery vocabulary items flagged by learners for exploration, showing word, context, definition, examples, grammar info, and exploration status. See which words learners encounter organically.

Instructions

Returns mystery vocabulary items — words learners encountered and flagged for exploration. Shows word, context, definition, examples, grammar info, and whether the learner has explored it. Useful for understanding organic vocabulary discovery.

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": "cl_get_mystery_items"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max results (default 30)
`explored`	No	Filter by exploration status

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 30, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The readOnlyHint annotation already covers the safety profile, and the description adds useful behavioral context by explaining what the returned items represent and which attributes are included. It also clarifies the explored-status distinction, which helps an agent understand the tool's semantics beyond a bare 'get items' label.

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 short, front-loaded with the main action, and structured with a clear field list in the second sentence. The final sentence adds a general use case but is somewhat vague; still, the overall text is efficient and easy to parse.

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 simple read-only getter with two optional parameters and no output schema, the description covers the key return fields and the exploring/explored distinction. It is mostly complete, though a bit more detail about the exact response shape or ordering would help since no output schema is provided.

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 parameter descriptions for 'limit' and 'explored' already provide the necessary semantic meaning. The description references the explored concept but does not add material detail beyond the schema, so a baseline score of 3 is appropriate.

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 ('Returns') and a specific resource ('mystery vocabulary items'), then enumerates the included fields (word, context, definition, examples, grammar, explored status). This is clear, but it does not explicitly differentiate the tool from its many get_* siblings, such as cl_get_content or cl_get_error_patterns.

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 phrase 'Useful for understanding organic vocabulary discovery' implies a use case but does not specify when to choose this tool over alternatives or when not to use it. There is no explicit guidance on selecting it among the sibling tools, though the purpose is understandable.

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