Skip to main content
Glama

Forge Engine

by app.forgeengine

update_system

Propose a system UPDATE → Inbox diff. get_system first; send the FULL revised spec. new_title renames; context_title+context bundles the Idea update. Set resync:true ONLY when you rewrote this spec FROM its upstream Idea (see resync_from_idea) — it re-stamps the staleness signal on adopt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoPreferred
nameNoIf no id
specYesFull revised spec markdown
resyncNoThis spec was re-derived from its upstream Idea — re-stamps sourceSig on adopt. Never set it on an ordinary edit.
contextNoFull revised Idea text
new_titleNoRename in the same card
project_idNo
context_titleNoIdea section to also update
acknowledge_rejectionNoOnly after a DECLINED bounce AND asking the user

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / resync
      Added value: +{
+  "description": "This spec was re-derived from its upstream Idea — re-stamps sourceSig on adopt. Never set it on an ordinary edit.",
+  "type": "boolean"
+}
  2. Changed9 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / acknowledge_rejection / description
      Previous value: -"Only when a previous call bounced with 'the owner DECLINED this': pass true AFTER asking the user. Never pass it just to get past the gate."New value: +"Only after a DECLINED bounce AND asking the user"
    • changedInput schema / properties / context / description
      Previous value: -"Optional — the full revised Idea/Context text (markdown) for `context_title`, sent in the same call to keep source-of-truth in sync. Requires `context_title`."New value: +"Full revised Idea text"
    • changedInput schema / properties / context_title / description
      Previous value: -"Optional — to ALSO update the upstream Idea: the Context section title to match (Title Case, English). Pair with `context`. Find it via get_system (`sources`) / search."New value: +"Idea section to also update"
    • changedInput schema / properties / id / description
      Previous value: -"System id from get_project_context (preferred)"New value: +"Preferred"
    • changedInput schema / properties / name / description
      Previous value: -"Exact existing system name (if no id)"New value: +"If no id"
    • changedInput schema / properties / new_title / description
      Previous value: -"Optional — also RENAME this system to this title in the same update card (e.g. to fix a wrong/changed name on a re-import). Omit to keep the current name."New value: +"Rename in the same card"
    • removedInput schema / properties / project_id / description
      Removed value: -"Project id (from list_projects) to act on; omit = the connector URL's project."
    • changedInput schema / properties / spec / description
      Previous value: -"Full revised spec markdown (## Goal / ## Boundary / ## Acceptance)"New value: +"Full revised spec markdown"
  3. Changed1 schema field changed
    • addedInput schema / properties / acknowledge_rejection
      Added value: +{
+  "description": "Only when a previous call bounced with 'the owner DECLINED this': pass true AFTER asking the user. Never pass it just to get past the gate.",
+  "type": "boolean"
+}
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description discloses that this tool creates a proposal (Inbox diff) rather than a direct mutation, which is critical behavioral context. It also explains the resync behavior ('re-stamps the staleness signal on adopt') and adds a caution ('Never set it on an ordinary edit'). With only destructiveHint:false provided, the description adds substantial behavioral context.

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 description is three sentences, front-loaded with the primary purpose, and every sentence adds critical operational detail. It is dense but not verbose, with no filler or redundancy.

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 9-parameter tool with no output schema, the description covers the most nuanced behaviors: the proposal/inbox-diff pattern, the need to fetch the system first, the resync condition, and the rename/bundle parameters. Remaining parameters (acknowledge_rejection, project_id) are covered by the schema, so the description is sufficiently complete.

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 high (89%), but the description goes beyond schema by clarifying the purpose of new_title ('renames'), context_title+context ('bundles the Idea update'), and resync ('ONLY when you rewrote this spec FROM its upstream Idea'). It also emphasizes that spec must be the 'FULL revised spec,' which is not fully captured in the schema's 'Full revised spec markdown'.

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?

The description opens with 'Propose a system UPDATE → Inbox diff,' which clearly states the verb (update), the resource (system), and the resulting artifact (inbox diff). This distinguishes it from siblings like propose_system, update_element, and update_task, which target different resources or actions.

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?

The description gives explicit sequential guidance: 'get_system first' and 'send the FULL revised spec.' It also conditionally references resync_from_idea ('see resync_from_idea') and clearly states when resync:true should be used. It does not explicitly list alternatives for when to use propose_system, but the purpose statement makes that distinction obvious.

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

All Forge Engine toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose, with explicit distinctions between direct actions and proposals via Inbox. The verbs and object types (system, milestone, screen, element, balance) are unique enough that no two tools appear to do the same thing.

Naming Consistency4/5

Most tool names follow a consistent verb_noun snake_case pattern (get_system, propose_screen, update_element). Minor deviations like 'dedupe', 'search', 'next_task', and 'reorder' are single words or non-verb but remain readable and stylistically compatible.

Tool Count1/5

With 54 tools, this server vastly exceeds the typical MCP scope, hitting the 'extreme mismatch' threshold. Even for a complex domain, the sheer number will overwhelm agents and degrade selection performance.

Completeness5/5

The tool surface is remarkably complete, covering full lifecycle operations for all major entities, plus import, design generation, drift detection, status reporting, inbox handling, and rejection workflows. No obvious dead ends or missing operations for the stated purpose.

Resources