list_lessons
List lesson metadata. Filter by level/category.
Args:
level: 'junior' | 'senior' | 'vidwat'.
category: e.g. 'theory-1', 'practical-1', etc.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| level | No | ||
| category | No |
VenuVidya — Carnatic Flute Study Guide
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so description must disclose behavioral traits. It states the operation (list, filter) but omits return format (e.g., what 'metadata' includes), pagination, rate limits, or side effects. This is insufficient for a listing tool with no output schema.
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 concise (two sentences plus args list) and front-loaded with purpose. No wasted words; structured cleanly with args in a bullet-like format.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and sibling tools, the description lacks completeness. It does not specify default behavior (e.g., what happens with no filters), return structure, ordering, or pagination, which are critical for a listing tool.
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?
Schema description coverage is 0%, but the description provides possible values for 'level' and an example for 'category', adding meaning beyond the schema. It compensates well for the lack of schema descriptions.
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?
Description uses specific verb 'List' and resource 'lesson metadata', and mentions filtering by level/category. This clearly distinguishes it from siblings like get_lesson (single lesson) and list_classes (different resource).
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 description implies usage for listing/filtering lessons but does not explicitly state when to prefer this over siblings like get_lesson or search_syllabus. No direct comparison or exclusion criteria provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: ask_venuvidya is a RAG chatbot, search_syllabus is keyword search, list/get_lesson and list/get_class handle distinct resources, and log_practice_session writes practice data. No two tools have overlapping responsibilities.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case (ask, get, list, log, search). Even 'ask_venuvidya' uses a verb + proper noun, matching the style. Naming is predictable and scannable.
Tool Count5/5
Seven tools cover the core flows of a study guide: browsing lessons, searching content, logging practice, and retrieving class journals. This is well-scoped—not too sparse, not bloated.
Completeness4/5
The surface covers viewing lessons and classes, searching, and logging practice, but lacks write operations for lessons or classes (e.g., annotating or updating). However, the server's role is a study guide, and the missing operations are not essential for its stated purpose.