Skip to main content
Glama

hjarni

by com.hjarni
OverviewDiscussionsAdmin

instructions-update

Destructive

Update LLM instructions at the specified level. Required: level ('brain'|'personal_root'|'container'|'team'), instructions (string). Optional: id (integer, required for 'container' and 'team'), mode ('replace' default|'append'). The 'container' level updates personal containers only; to set instructions for a team, use level 'team' (team owners only). In 'replace' mode (default), the provided text overwrites existing instructions. In 'append' mode, the text is appended to existing instructions with a newline separator. Always read current instructions first before replacing to avoid losing existing content.

Input Schema

NameRequiredDescriptionDefault
idNoContainer ID or Team ID (required for 'container' and 'team' levels)
modeNoUpdate mode: 'replace' (default) overwrites existing instructions, 'append' adds to them
levelYesInstruction level to update (required)
instructionsYesThe instructions text. In 'replace' mode (default), this overwrites existing instructions. In 'append' mode, this is appended to existing instructions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / instructions / description
      Previous value: -"The full updated instructions text. This replaces the existing instructions entirely."New value: +"The instructions text. In 'replace' mode (default), this overwrites existing instructions. In 'append' mode, this is appended to existing instructions."
    • changedInput schema / properties / level / description
      Previous value: -"Instruction level to update"New value: +"Instruction level to update (required)"
    • addedInput schema / properties / mode
      Added value: +{
+  "description": "Update mode: 'replace' (default) overwrites existing instructions, 'append' adds to them",
+  "enum": [
+    "replace",
+    "append"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond annotations: replace mode overwrites existing content, append uses a newline separator, and team-level updates are restricted to team owners. With destructiveHint already covering the safety profile, the description enriches it with what actually gets overwritten and the permission boundary, though it doesn't cover failure modes or idempotency.

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?

Purpose and required fields are front-loaded, then constraints and mode semantics follow in a logical order. It is somewhat dense but every sentence carries actionable information; no 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 mutation tool with no output schema and full annotation coverage, the definition supplies level semantics, id requirements, permission limits, and mode behavior, which is nearly everything needed to call it correctly. Return handling is unaddressed but low-risk for a mutation.

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 baseline is 3, but the description adds genuine meaning: it clarifies which levels require id, that 'container' means personal containers only, and how mode's replace-vs-append behave. This goes beyond the schema field descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Update LLM instructions') plus the scope ('at the specified level'), so an agent immediately understands the operation. It clearly implies the write counterpart to instructions-get without explicitly naming it, so sibling differentiation is present but not spelled out.

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?

Gives explicit when-to-use guidance with alternatives and prerequisites: 'container' updates personal containers only, team instructions must use level 'team' (team owners only), and 'Always read current instructions first before replacing.' Alternative path and precondition are both stated.

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

All hjarni toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources