Keyword (BM25) search across all Carnatic flute lessons.
Args:
query: Natural-language question or keywords (English or Kannada).
k: Number of top results to return (1-10, default 4).
level: Optional filter — 'junior', 'senior' or 'vidwat'.
| Name | Required | Description | Default |
|---|---|---|---|
| k | No | ||
| level | No | ||
| query | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses the search algorithm (BM25) and parameters. It does not explicitly state side effects or read-only nature, but for a search tool this is reasonably transparent. The mention of BM25 adds behavioral detail.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single clear sentence followed by a structured parameter list. Every sentence adds value, and the key information is front-loaded. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the low complexity, no output schema, and no annotations, the description covers the core functionality and parameter usage. It lacks details about output format or ordering, but for a simple search tool with k results it is adequately complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description compensates fully by explaining each parameter: query as natural-language query, k as number of results (1-10, default 4), and level as optional filter with specific values (junior, senior, vidwat). This adds significant meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it's a 'Keyword (BM25) search across all Carnatic flute lessons', which is a specific verb and resource. It distinguishes from sibling tools like get_lesson (individual retrieval) and ask_venuvidya (likely Q&A).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for searching across lessons but does not explicitly state when to use versus alternatives (e.g., ask_venuvidya for questions, list_lessons for overview). No when-not or alternative guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.