Skip to main content
Glama

List Course Sections

list_course_sections
Read-onlyIdempotent

Fetch course sections from a Circle community with paging, sorting, and optional bounded all_pages; each request uses API quota.

Instructions

List Course Sections. Reads community data. Supports bounded all_pages; every page counts against the API quota.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
sortNoSorting parameters (sort by name in ascending order, name in descending order, and by newest. Default is oldest)
accountNoNamed private Circle account; selects credentials, not a remote community ID.
per_pageNoNumber of records per page
space_idNoSpace ID of the course section
all_pagesNoRead bounded page/per_page pages; each request consumes API quota. Not a snapshot or guaranteed complete backup.
max_itemsNoMaximum returned records with all_pages=true, default 1000. At most 100 requests; output includes continuation state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint/destructiveHint=false, so the safety profile is covered. The description adds quota behavior beyond that: "every page counts against the API quota" and "supports bounded all_pages" — genuinely useful operational context about rate/cost implications.

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?

Three short sentences, front-loaded with the purpose and quota constraint. However, the opening sentence duplicates the tool name/title and carries no added value.

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

Completeness3/5

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

With no output schema, the description could say something about what a returned section contains, and it never clarifies list-vs-get selection. Quota and bounded-pagination context is present, but return-value shape and sibling routing are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 7 parameters (page, sort, account, per_page, space_id, all_pages, max_items), including the all_pages quota note. The description echoes rather than extends this, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List Course Sections" restates the tool name/title almost verbatim, so the purpose is clear (list, course sections) but the description adds no differentiation from siblings like get_course_section or list_course_lessons. The appended "Reads community data" hints at scope but does not distinguish this tool's role.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives (get_course_section, list_course_lessons, search), and no prerequisites or exclusions. "Reads community data" is context, not usage guidance.

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

Deploy Server

Other Tools