list_study_topicsThe catalog behind the other tools: indexed subjects/topics (for search_sambodh_knowledge and quiz subject filters), available PYQ years, published current-affairs month slugs, and NewsPulse GS-paper values. Call this first when unsure which parameter values are valid.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint. The description adds useful context by enumerating the specific data categories returned (subjects, PYQ years, month slugs, GS-paper values), which goes beyond the annotations. However, it does not describe the output structure or potential list size.
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 compact sentence plus a short directive. It front-loads the tool's role and lists its contents without unnecessary verbosity. Every clause adds value.
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?
For a read-only, zero-argument catalog tool, the description covers both the returned data categories and when to call the tool. Although no output schema exists, the enumerated categories give sufficient expectation of the response. The context from annotations and sibling tools completes the picture.
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?
The tool has zero parameters, so the baseline is 4. The description does not need to explain parameter details; instead, it explains the content categories that become valid parameter values for other tools, which is meaningful semantics.
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 the tool is 'the catalog' that lists indexed subjects/topics, PYQ years, current-affairs month slugs, and NewsPulse GS-paper values. It explicitly distinguishes itself from siblings by being the parameter-value reference for search_sambodh_knowledge and quiz filters.
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?
Provides an explicit usage directive: 'Call this first when unsure which parameter values are valid.' It also frames the tool as 'the catalog behind the other tools,' making its role relative to siblings clear.
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 addresses a distinct task: current affairs listing vs. detail, PYQ sample, topic catalog, knowledge search, and quiz start/submit. There is no functional overlap between the tools, and descriptions make the boundaries clear.
All tool names follow a consistent verb_noun pattern using snake_case (get_, list_, search_, start_, submit_). The naming scheme is predictable and easy to infer.
With 7 tools, the set is well-scoped for an IAS preparation server. Each tool serves a clear purpose, and the count is within the ideal range for a focused domain.
The toolset covers core UPSC prep needs: current affairs, static knowledge search, PYQ sampling, and quiz practice. The only minor gap is the lack of full PYQ papers, but the sample tool intentionally points to the platform for complete sets.