Daily Tutor MCP

Overview Schema Source Related Servers Discussions Admin

set_topic

Add or update a single practice topic, including its level, subtopics, and automatic difficulty adjustment; setting a level manually restarts adaptation from that point.

Instructions

Add or update ONE topic: its level, its subtopics (replaces the list), and whether the level adapts automatically (auto_adjust). Setting a level manually restarts adaptation from now.

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": "set_topic"
  }
}

Input Schema

Name	Required	Default
`name`	Yes
`level`	No
`user_id`	No	default
`subtopics`	No
`auto_adjust`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose two important side effects unprompted: 'subtopics (replaces the list)' is a destructive overwrite, and 'Setting a level manually restarts adaptation from now' changes ongoing state. It still omits scoping behavior for user_id and what happens to unspecified fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly packed sentences, front-loaded with the primary action, with the two caveats (list replacement, adaptation reset) placed where they are read before invocation. No filler.

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, so return values need not be explained. But for a 5-param mutation with 0% schema coverage, the description leaves user_id undefined and never indicates what values 'level' accepts, which an agent needs to call this correctly.

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 coverage is 0%, so the description must compensate, and it does for four of five params: level, subtopics (replace semantics), and auto_adjust are given real meaning. user_id is never mentioned, and no valid values for the free-form 'level' string are given, keeping it short of a 5.

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 states a specific verb ('Add or update') and resource ('ONE topic') and enumerates the mutable facets (level, subtopics, auto_adjust). The 'ONE' emphasis hints at single-topic granularity, but no sibling (e.g. remove_topic) is named to sharpen the contrast.

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?

The 'Add or update' framing implies upsert usage, so an agent can infer the tool is for creating or changing a topic. However, there is no explicit guidance on when to use this vs remove_topic, set_preferences, or other configuration siblings, and no prerequisites are stated.

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