Skip to main content
Glama

create_tutor_course

Create a new draft structured course or class curriculum.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_tutor_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCourse title
levelNoSkill or grade level label
endsOnNoCourse end date (YYYY-MM-DD)
startsOnNoCourse start date (YYYY-MM-DD)
descriptionNoCourse syllabus or overview
requiresLevelApprovalNoRequire instructor approval before enrollment

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety and mutation profile is covered. The description's one added behavioral fact is that the course is created in 'draft' state, which is genuinely useful and not in the annotations. It says nothing about enrollment visibility, permissions, or duplicate-name handling, so the added value is real but thin.

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 or redundancy. It is efficient, though its brevity borders on under-specification given the tool performs a mutation with six parameters.

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?

An output schema exists and the input schema is fully described, so the description needn't explain returns or fields. What is missing is context an agent needs for correct sequencing: whether the created course is invisible until published, and whether requiresLevelApproval has side effects on enrollment. Adequate but with a noticeable gap for a creation tool.

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%, with every one of the six properties carrying its own description (title, level label, start/end dates in YYYY-MM-DD, syllabus, level-approval flag). The description adds no format hints, defaults, or constraints beyond that, so the baseline of 3 applies.

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 plus resource ('Create a new draft structured course or class curriculum'), which is enough to distinguish it from the read siblings get_tutor_course and list_tutor_courses. It doesn't, however, explicitly contrast itself with any other creation tool or state that the result is a tutor course object rather than a generic curriculum entity.

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 guidance on when to call this versus list_tutor_courses/get_tutor_course, no mention of prerequisites, and no note on what to do after creation (e.g., publishing the draft). The only implied usage is 'call this to make a course,' which an agent could infer from the name alone.

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.