Skip to main content
Glama

scobees_patch_arbeitsblatt

Updates a worksheet in place by replacing each specified old string with new text in its Markdown, applying changes only if every old string occurs exactly once and reporting any failed replacements.

Instructions

Ändert das Arbeitsblatt einer Aufgabe gezielt, statt es komplett neu zu senden: ersetzt im aktuellen Markdown jede angegebene Zeichenkette durch eine neue. Alles-oder-nichts – jede „alt“-Zeichenkette muss genau einmal vorkommen, sonst wird nichts geändert und die Meldung nennt jede fehlgeschlagene Ersetzung (nicht gefunden/mehrfach gefunden). Nur möglich, wenn das Arbeitsblatt verlustfrei als Markdown darstellbar ist (keine Bausteine wie Bild-Zuordnung ohne Markdown-Entsprechung); sonst Fehlermeldung mit Verweis auf scobees_get_aufgabe(mit_serlo_json) + scobees_update_aufgabe(serlo_json).

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": {
      "id": "<id>",
      "ersetzungen": "<ersetzungen>"
    },
    "name": "scobees_patch_arbeitsblatt"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAufgaben-ID (LI-…)
ersetzungenYesJe ein Paar alt/neu; „alt“ muss im aktuellen Arbeitsblatt-Markdown genau einmal vorkommen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.10

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses all-or-nothing atomicity, the exactly-once matching constraint, and that the error message enumerates each failed replacement by cause (not found / found multiple times). It omits auth/permission requirements and what a successful response contains, which keeps it short of a 5.

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 sentences, front-loaded with the intent before the mechanism, the atomicity rule, and the fallback chain. Dense but every clause carries operational information; the nested parenthetical about 'Bausteine' costs some readability.

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 two-parameter mutation tool with no annotations and no output schema, the description covers preconditions, failure semantics, and the fallback route thoroughly. The one remaining gap is the success payload — whether the updated markdown or just a confirmation is returned — which nothing else in the definition supplies.

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 both parameters are already documented in the schema, including the exactly-once rule for 'alt'. The description adds only that each supplied pair is applied as one replacement pass and that failures are reported per pair — useful framing, but largely restating 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 ('Ändert das Arbeitsblatt einer Aufgabe') and immediately scopes it against the alternative ('statt es komplett neu zu senden'), then defines the mechanism (string replacement in current markdown). An agent can distinguish this from scobees_update_aufgabe 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?

Explicitly frames the choice as targeted patch vs. full resend, states the blocking precondition (worksheet must be losslessly representable as markdown), and names the exact fallback path (scobees_get_aufgabe(mit_serlo_json) + scobees_update_aufgabe(serlo_json)). When-to-use, when-not, and alternatives are all present.

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