Skip to main content
Glama

list_sections

Return the knowledge-base taxonomy with page counts: sections, grades, subjects, and how-to categories. Use this to browse available entries before calling list_questions. No input required. Read-only.

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_sections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does declare 'No input required. Read-only,' covering the safety profile an agent needs. It stops short of describing the response shape (nesting, ordering, whether counts are totals or filtered), which is the main remaining gap.

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 short sentences with zero filler: the return content is front-loaded, the usage guidance follows, and the behavioral note closes. Every sentence earns its place.

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?

For a no-parameter, no-output-schema, read-only tool, the description covers returned content and the correct usage sequence, which is nearly everything an agent needs. Only the detailed shape of the returned taxonomy (hierarchy, ordering, count semantics) is left unspecified.

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, which is the baseline-4 case, and the description explicitly confirms 'No input required,' so there is no ambiguity about arguments. Nothing further is needed on this dimension.

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 gives a specific verb and resource ('Return the knowledge-base taxonomy') and enumerates the exact contents: sections, grades, subjects, and how-to categories with page counts. That makes it clearly distinct from question-oriented siblings like list_questions or search_questions without needing their schemas.

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 states an explicit use case and ordering ('Use this to browse available entries before calling list_questions'), which routes the agent to the correct follow-up tool. It does not name any situation where this tool should be avoided, but for a zero-param taxonomy lister there is little else to exclude.

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