Skip to main content
Glama

ask_tutor

Ask Course Tutor Cynthia a course-content question about a topic covered in a Planet Leads Academy course. She answers ONLY from the verified lesson text of the 35 Academy courses (280 lessons), returning a verbatim excerpt from the matching lesson, cited as (Course name — Lesson N: Lesson title). If no lesson matches confidently, she honestly says she does not have verified material on that yet instead of guessing. For questions about Cynthia, Planet Leads, prices, or policies, use ask_cynthia instead.

Args:
    question: The course-content question, in plain English.

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": {
      "question": "<question>"
    },
    "name": "ask_tutor"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the grounding strategy (verified lesson text only), the knowledge boundary (35 courses, 280 lessons), the output contract (verbatim excerpt cited as Course name — Lesson N: title), and the graceful-failure behavior (says it lacks verified material instead of guessing). These are exactly the traits annotations would otherwise need to provide.

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?

The body is front-loaded and dense with useful facts in four sentences with no filler. The trailing 'Args: question:' block adds little over the schema and mildly dilutes the otherwise clean structure.

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

Completeness5/5

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

An output schema exists, so return values need not be explained, yet the description still sketches the answer shape and citation format. Combined with the grounding limits and failure behavior, an agent has everything needed to call this correctly and interpret the result.

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 description coverage is 0% and the schema only declares a bare string named 'question', so the description must compensate. It does by specifying the expected content (a course-content question) and the expected form (plain English), which meaningfully constrains inputs beyond the schema, though it does not discuss length, ambiguity, or how to phrase a lesson-specific query.

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 (ask the Course Tutor a course-content question) and bounds the scope to the 35 Academy courses / 280 lessons. It explicitly contrasts itself with the sibling ask_cynthia, so an agent can choose between them without opening 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 Guidelines5/5

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

Gives both the when-to-use condition (topics covered in a Planet Leads Academy course) and the when-not-to-use condition with a named alternative (questions about Cynthia, Planet Leads, prices, or policies go to ask_cynthia). Nothing about routing is left to inference.

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