Skip to main content
Glama

list_tutor_courses

Read-onlyIdempotent

List structured courses and multi-session classes in the active company.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 25)
offsetNoOffset (default 0)
statusNoFilter by course status

Output Schema

NameRequiredDescriptionDefault
dataYesTool result payload — shape varies per tool, see the tool description
summaryYesOne-line human-readable summary of the action
renderTypeYesUI rendering hint for the result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds one piece of behavioral context beyond that — results are scoped to the "active company" — but says nothing about default status filtering (e.g. whether archived courses appear), result ordering, or pagination behavior.

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?

A single front-loaded sentence with no filler; the scoping constraint is stated up front. It is efficient but extremely terse, offering no structural cues such as defaults or alternatives.

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 simple three-parameter, zero-required list tool with a full output schema and rich annotations, the description covers what is listed and the tenant scope. The remaining gaps (default status behavior, pagination expectations) are largely absorbed by the schema documentation.

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 limit, offset, and the status enum are already fully documented in the schema. The description contributes only the implicit company scoping and adds no meaning about how status filtering interacts with the listing. Baseline 3 applies when the schema carries the parameter burden.

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

Purpose4/5

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

The description gives a specific verb ("List") and a specific resource ("structured courses and multi-session classes"), plus a scoping qualifier ("in the active company"). It implicitly distinguishes itself from the create_/get_ siblings by being the enumeration form, but it never names a sibling to make that differentiation explicit.

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

Usage Guidelines3/5

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

Usage is only implied by the verb "List" — an agent can infer it is for browsing/enumerating courses rather than fetching one. There is no statement of when to prefer this over get_tutor_course for a single record, and no mention of prerequisites, default filtering behavior, or how to page through results.

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.