Skip to main content
Glama

Courses

zarok_get_courses
Read-onlyIdempotent

Returns the user’s courses with their ids, reminder times, phases (active and pause periods with the user’s own short text), and start and end dates. Use these ids in update_course and stop_course operations. 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": "zarok_get_courses"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so "Read-only" in the description is confirmatory rather than new. The genuinely additive content is the disclosure of what the response contains — phases as active/pause periods carrying the user's own short text — which is meaningful since there is no output schema.

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?

Two sentences, no padding, with the returned-field enumeration front-loaded and the follow-up call guidance second. The trailing "Read-only." is a small redundancy against the annotations and could have been folded elsewhere, but it costs little.

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?

With no output schema, the description carries the return contract, and it does so adequately by naming the fields exposed. It does not mention ordering, empty-state behavior when the user has no courses, or the shape of the phase objects, which would be useful for a collection-returning tool.

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 there is no parameter meaning for the description to supply; the schema's empty object is fully self-explanatory. Baseline for a no-parameter tool applies.

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 opens with a specific verb and resource ("Returns the user's courses") and enumerates the exact fields returned: ids, reminder times, phases with the user's own short text, and start/end dates. This clearly separates it from siblings like zarok_get_habits, zarok_get_meals, and zarok_get_plan, which cover other domains.

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 explicitly states a downstream use case: "Use these ids in update_course and stop_course operations," which tells an agent this is the prerequisite discovery step. It stops short of saying when-not-to-use or how it relates to aggregate siblings such as zarok_get_week_summary, leaving a small gap.

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