Daily Tutor MCP

Overview Schema Source Related Servers Discussions Admin

skip_question

Skip a practice question without earning XP or extending a streak; the skipped question still counts toward the current session's length.

Instructions

The user skipped the question: no XP, no streak. Counts toward a session's length.

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_id": "<question_id>"
    },
    "name": "skip_question"
  }
}

Input Schema

Name	Required	Description	Default
`user_id`	No		default
`question_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 2, 2026

TDQS

C2.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful side effects: no XP awarded, streaks unaffected, and the skip counts toward session length. However, it omits whether the question is marked as missed, whether it can be retried, or any permission requirements.

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 short clauses with no wasted words, and the key behavioral facts are front-loaded. The fragmentary sentence structure is slightly awkward but efficient.

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

Completeness2/5

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

A mutation-style tool with no annotations, no output schema, and undocumented parameters needs more than this fragment. The description does not explain the effect on the pending-question state or what the caller receives in return.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters. The description implies a question is identified ('the question') but never documents question_id's expected value, and says nothing about the user_id parameter or its 'default' semantics, so it fails to compensate for the coverage gap.

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

Purpose3/5

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

The description identifies the operation as skipping a question and states its consequences (no XP, no streak), but the phrasing 'The user skipped the question' reads as a status statement rather than an instruction, leaving ambiguity about whether the tool records a skip or reports one. It does not distinguish this from siblings like save_question or check_answer that also act on a pending question.

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 explicit guidance on when to call this tool versus alternatives such as check_answer or save_question, nor any mention of prerequisites (e.g., that a pending question must exist). The agent must infer usage entirely.

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