Skip to main content
Glama

AIML Rounds

Search lessons

search
Read-only

Search AIML Rounds lessons by keywords or an interview question. Filter by track (fundamentals, ai-engineering, system-design, papers), type (concept, interview, design, paper) or section/part name. Returns lesson ids for get_lesson.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoconcept = lesson, interview = scenario set, design = system design question, paper = paper explained
limitNo
queryYesKeywords or a question, e.g. 'KV cache', 'why does RAG retrieve the wrong chunk'
trackNo
sectionNoPart or section name to filter by, e.g. 'RAG', 'LLMs', 'Recommendation Systems'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already state readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the genuinely useful behavioral fact that results are lesson ids only, meaning a second call to get_lesson is required to read content — the kind of chaining context annotations cannot express. It stops short of describing ranking or how partial matches behave.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly packed sentences: purpose, then filters, then return shape. The most actionable information (what it searches and what it returns) leads each sentence, and nothing is redundant.

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?

No output schema exists, and the description correctly compensates by specifying that ids are returned for use with get_lesson. Filter dimensions are complete against the schema. The only gap is result-count behavior — the limit parameter (default 8, max 30) is never surfaced in prose.

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?

With 60% schema coverage, the description adds real value by enumerating the track values (fundamentals, ai-engineering, system-design, papers), which the schema leaves undocumented, and by giving the section filter concrete examples ('RAG', 'LLMs'). The type enum meanings largely restate the schema, and limit is never mentioned in the description.

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 states a specific verb and resource ('Search AIML Rounds lessons') and scopes the input mode to keywords or an interview question, which distinguishes it from browse (catalog listing) and get_lesson (fetch by id). It also declares the output form ('lesson ids'), so an agent knows exactly what comes back.

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

Usage Guidelines4/5

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

It makes clear when to use this tool (you have keywords or a natural-language question and need matching lessons) and names the downstream step, get_lesson, for fetching content. It does not explicitly exclude browse for exploratory listing, but the search-vs-fetch split is unambiguous.

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.

Resources