Skip to main content
Glama

Save a teaching rule

save_rule

Store a lasting teaching preference as a rule so godspeed's tutor applies it to future lessons. Target one space or all lessons; undo or edit afterwards.

Instructions

Save a rule about how godspeed's teacher teaches this learner, when they tell you a lasting preference ("use Python for code examples", "shorter answers"). It joins the learner's rules in Settings, for every lesson or for one space's lessons, and applies from the next turn. Not for one-off requests or facts about the learner (use remember for those). Don't ask first: the godspeed window shows it with Undo and Edit.

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": {
      "rule": "<rule>"
    },
    "name": "save_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoFor every lesson, the part of teaching it is about: "voice", "teaching" (the default), "questions", "facts", "demos" or "files" (files, formatting and code).
ruleYesOne line, an instruction to the teacher, e.g. "Use Python for code examples."
space_idNoOnly for this space's lessons (from list_spaces). Leave it out for every lesson.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare the safety profile (not read-only, non-destructive, not idempotent); the description adds real behavioral context: the rule lands in Settings, can be scoped to all lessons or one space, takes effect from the next turn, and is undoable via the UI. The one gap is that idempotency is never addressed — it doesn't say whether saving an identical rule duplicates it — which matters given idempotentHint=false.

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?

Three tight sentences: what/when, where it lands and when it applies, then the exclusion and the no-confirmation instruction. Every clause carries information an agent would otherwise have to guess.

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?

For a mutation tool with annotations and a fully described three-parameter schema, the description covers effect timing, visibility, reversibility, scope selection, and sibling routing. Nothing essential to calling it correctly is missing.

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 coverage is 100%, so rule, area, and space_id are fully documented in the schema, including the enum values. The description reinforces the two scopes (every lesson vs. one space) and the one-line instruction style, but adds no format or constraint detail beyond the schema — baseline 3 applies.

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?

Names a specific verb and resource (save a teaching rule about how the teacher teaches this learner) and grounds it with two concrete example rules. It explicitly separates itself from the sibling remember tool, so an agent can choose 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?

States the trigger condition (the user voices a lasting preference), gives exemplar phrasings, and names the exclusion — one-off requests and facts about the learner go to remember. It even resolves the confirmation question with 'Don't ask first,' removing the most common agent hesitation.

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