Skip to main content
Glama

Change a prep sheet

update_prep
Idempotent

Modifies a learner’s preparation sheet on request: move or clear the day, replace its description, change mock settings, and add or remove topics by ID while sending only changed fields.

Instructions

Change a prep's sheet when the learner asks (read_space shows it): move or clear its day, replace what it is like, change what a mock is, add topics, or remove topics by id. Only what you send changes. Refused while the sheet is being written.

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": {
      "space_id": "<space_id>"
    },
    "name": "update_prep"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoThe day it happens as YYYY-MM-DD, or null for no day.
mockNoWhat one mock is: how many questions in how many minutes.
aboutNoWhat it is like, in markdown. Replaces the whole text.
space_idYes
add_topicsNoTopics to add at the end of the sheet, each with one line on why it is there.
remove_topic_idsNoIds of the sheet's topics to remove.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the description adds real value with 'Only what you send changes' (partial-patch semantics) and 'Refused while the sheet is being written' (a lock/concurrency condition nowhere in the schema or annotations). It omits what a successful update returns, but with no output schema that is a minor gap against the safety profile already covered.

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?

Three short sentences, front-loaded with the action and the read_space pointer, and the patch-semantics caveat lands before the refusal note. Slightly awkward phrasing ('a prep's sheet') and the operation list is dense, but nothing is filler.

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 6-parameter mutation tool with a nested mock object and no output schema, the description covers the trigger, the patch semantics, every editable facet, and the refusal condition. The main omission is any hint of what the tool returns after updating, which matters more here because no output schema exists.

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 83%, so the baseline is 3, and the description earns an extra point by tying each operation to its parameter in plain language ('move or clear its day' for date, 'replace what it is like' for about, 'change what a mock is' for mock, add/remove for the two topic arrays). It still leaves 'why' on added topics and the exact id source for remove_topic_ids 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 (change) and resource (a prep's sheet), then enumerates exactly what can be changed: day, about text, mock, add topics, remove topics by id. Each enumerated operation maps to a distinct capability, so an agent can tell it apart from read_space (reading) and update_space (space-level settings).

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?

Explicitly frames the trigger ('when the learner asks') and points at read_space as the tool that shows the sheet, which routes the agent correctly. It does not spell out a when-not case beyond the concurrent-write refusal, so it stops short of full alternative routing.

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