Skip to main content
Glama

Edit a concept

update_content
Destructive

Change an existing concept's content: add text to the end with append, or replace a passage with old and new. Earlier versions stay in the history and can be restored on aisoulkeeper.com.

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": {
      "concept": "<concept>"
    },
    "name": "update_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
newNoThe replacement for old.
oldNoThe exact text to replace, copied from read_concept. For a long passage, write its start and end joined by '...'. Needs new.
appendNoText to add to the end. Use instead of old and new.
conceptYesThe concept's name, one of its other names, or its ID.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

The annotations already flag this as destructive and not read-only. The description adds useful behavioral context beyond that: earlier versions remain in history and can be restored on aisoulkeeper.com, which tells the agent the edit is recoverable. It does not cover permissions, failure behavior, or whether changes are atomic.

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?

The definition is two tight sentences with the core action front-loaded. It uses only the wording needed to explain the edit modes and the history/recovery behavior.

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 four-parameter mutation tool with full schema coverage and destructive annotations, the description supplies the essential editing modes and recovery context. Minor gaps around error behavior and mutual exclusivity are partly handled by the schema, so the definition is largely complete.

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 the schema already documents all four parameters in detail. The description restates the append and old/new usage at a high level but adds little syntax or constraint detail beyond what the schema provides, making the baseline 3 appropriate.

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?

The description gives a specific verb and resource: changing an existing concept's content. It clearly names the two edit modes, append and replace via old/new, but does not explicitly differentiate this tool from siblings such as set_concept or create_concept.

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?

It clearly explains when to use append versus old/new for replacing a passage. It does not state when to avoid this tool or name alternatives, but the context for the two supported editing modes is explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources