CampusMind-AI

Overview Schema Source Related Servers Discussions Admin

demo_backdate_topic

Simulate past reviews by backdating a concept's last-reviewed timestamp, enabling testing of review-due calculations without real-time waiting.

Instructions

DEMO/TESTING ONLY: artificially age a concept's last-reviewed timestamp by N days so get_review_due can be tested without waiting real time.

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": {
      "studentId": "<studentId>",
      "conceptId": "<conceptId>"
    },
    "name": "demo_backdate_topic"
  }
}

Input Schema

Name	Required	Description
`daysAgo`	No	How many days to age the last-reviewed timestamp (default 5)
`conceptId`	Yes	The concept ID to backdate
`studentId`	Yes	The student ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 31, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool mutates the last-reviewed timestamp and is for testing only, which is useful. However, it doesn't specify whether the change is reversible, impacts other data, or requires special permissions, leaving some behavioral ambiguity.

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?

The description is a single, well-structured sentence that front-loads the demo/testing intent and concisely states the function and rationale. Every word adds value, with no redundancies.

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?

Given the tool's simplicity and lack of output schema, the description provides sufficient context for its intended use: it explains the purpose, the mutation, and the testing scenario. However, it omits any mention of return values or side effects, which is a minor gap for a write operation.

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%, so the baseline is 3. The description adds the purpose of the daysAgo parameter in context, but it doesn't provide additional semantic meaning beyond what the schema already states. The description itself doesn't elaborate on the parameters.

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 clearly states the tool's function: artificially aging a concept's last-reviewed timestamp by N days. It specifies the resource (concept) and the action, and explicitly mentions the use case of testing get_review_due, which distinguishes it from sibling tools.

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?

The description explicitly labels the tool as 'DEMO/TESTING ONLY' and explains that it exists to enable testing of get_review_due without waiting real time. This provides clear usage context, though it doesn't name alternative tools for non-testing scenarios.

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