Dexi Notes

Grade review

grade_review

Record how well the user recalled a note under review and reschedule it (SM-2 spaced repetition). Use after quizzing the user on a card from get_due_reviews: 1 if they forgot (comes back in ~10 minutes), 2 if it was a struggle, 3 for normal recall, 4 for effortless recall.

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": {
      "note_id": "<note_id>",
      "grade": "<grade>"
    },
    "name": "grade_review"
  }
}

Input Schema

Name	Required	Description
`grade`	Yes	1=Again (forgot) 2=Hard 3=Good 4=Easy
`intent`	No	One short sentence on what you're trying to accomplish for the user — helps improve these tools; optional, keep personal details out
`note_id`	Yes	Note UUID to grade

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 5, 2026
- removedInput schema / properties / intent / anyOf
```
Removed value: -[
-  {
-    "maxLength": 300,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / intent / default
```
Removed value: -null
```
- addedInput schema / properties / intent / maxLength
```
Added value: +300
```
- addedInput schema / properties / intent / type
```
Added value: +"string"
```
First observedOct 27, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare this is a non-destructive mutation, and the description adds the key behavioral fact that grading reschedules the note via SM-2, including the ~10 minute return interval for grade 1. It does not disclose the resulting intervals for grades 2-4 or which scheduling fields are overwritten, so it stops short of full transparency.

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 with the action, mechanism, prerequisite, and grading scale front-loaded; no filler or repeated text.

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?

For a small mutation tool with full schema coverage and an output schema, the description covers purpose, prerequisite, and grading semantics adequately. The main remaining gap is what grades 2-4 do to the schedule, which an agent might want to explain its choice to the user.

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 100%, so the baseline is 3; the description goes slightly beyond by explaining the scheduling consequence of grade 1 (~10 minutes), though its grade labels largely duplicate the schema's enum-style description. note_id and intent are left entirely to the schema.

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 ('Record how well the user recalled a note') and names the mechanism (SM-2 spaced repetition), which distinguishes it from sibling tools like update_note or get_due_reviews.

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?

Explicitly says when to call it ('after quizzing the user on a card from get_due_reviews'), naming the prerequisite sibling tool, and defines the full 1-4 grading scale with the consequence for the lowest grade.

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

All Dexi Notes tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?