Skip to main content
Glama

list_questions

Browse question pages in this knowledge base without a search query. Filter by section (education, how-to), grade (for education pages, e.g. '1' or 'k'), subject (e.g. 'math'), or category (for how-to pages, e.g. 'units', 'money', 'cooking'). Results are paginated. Use list_sections first to see available filters and counts. 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_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
gradeNoOptional education grade, e.g. '1', '8', 'k', or 'college'
limitNoPage size (default 25, max 50)
offsetNoNumber of matching items to skip (default 0)
sectionNoOptional section slug, e.g. 'education' or 'how-to'
subjectNoOptional education subject, e.g. 'math'
categoryNoOptional how-to category, e.g. 'units', 'money', 'cooking', 'tech', 'home'

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description does meaningful work: it declares the tool read-only and states that results are paginated. It doesn't describe rate limits, error behavior, or what a returned 'question page' contains, but the safety and pagination profile an agent needs is present.

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

Conciseness4/5

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

Four short sentences, front-loaded with the core purpose, then filters, then the prerequisite. Some example values ('units', 'money', 'cooking') duplicate the schema's own examples, which is mild redundancy but not bloat.

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 six-parameter, all-optional listing tool with no output schema, the definition covers purpose, filter domains, pagination, prerequisite discovery, and read-only safety. The main remaining gap is that it never hints at the shape of a returned question entry, which matters slightly since no output schema exists.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns an extra point by adding cross-field semantics the schema omits — that grade and subject apply to education pages while category applies to how-to pages, and that section selects between those two domains.

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 — browsing question pages in this knowledge base — and immediately scopes it with 'without a search query,' which cleanly separates it from search_questions. An agent can decide between the two without inspecting either schema.

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?

Explicitly frames the condition (no search query, filter-driven browsing) and directs the agent to call list_sections first to discover valid filters and counts. It stops short of naming search_questions as the alternative for query-based lookup, leaving that inference to the reader.

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