Skip to main content
Glama

list_topics

Read-only

Lists hadith topics and entry counts to help you identify the exact topic name required for topic-based hadith searches.

Instructions

List the topics hadiths are tagged with, and how many entries carry each.

Use it to find the exact topic name before search_hadiths(topic=...), which matches the name exactly.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
itemsYesMost used first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that: the result is a topic list annotated with entry counts, and the exact-match constraint on downstream lookups. It omits scale/pagination details, which keeps it at 4 rather than 5.

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?

Two short sentences, front-loaded with what the tool returns and followed by the routing instruction. No redundant restatement of the name, no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter list tool with an output schema already documenting return values, the description supplies everything an agent needs: what comes back, what it is for, and the exact-match caveat when chaining into search_hadiths.

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?

The tool takes zero parameters, so the baseline is 4; no parameter meaning needs explaining. The description does supply relevant semantic context for how the returned topic strings must be consumed elsewhere, which is a small bonus rather than a gap.

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?

States a specific verb and resource ('List the topics hadiths are tagged with') and adds the distinguishing output trait ('how many entries carry each'), so an agent knows this is a topic enumeration with counts rather than a search over hadiths, narrators, or biographies.

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

Usage Guidelines5/5

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

Explicitly prescribes the workflow: call this first to discover the exact topic name, then pass it to search_hadiths(topic=...), and warns that the match is exact. This tells the agent both when to use it and why the alternative tool alone is insufficient.

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