Skip to main content
Glama

forge_context_graph_update

Update a context graph by providing a new version with state definitions, guidelines, and initial states to control agent conversation flow.

Instructions

Update a context graph by creating a new version. All fields are required. The terminal state must have exactly one action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
context_graph_idYesThe context graph ID to update
descriptionYesDescription of the conversation flow
new_user_initial_stateYesState name for new users (must be an action state, alphanumeric and underscores only)
returning_user_initial_stateYesState name for returning users (must be an action state, alphanumeric and underscores only)
terminal_stateYesName of the terminal state (must have exactly one action, alphanumeric and underscores only)
referencesNoReferences to other state machines: { ref_name: [machine_id, version] }
global_intra_state_navigation_guidelinesYesNavigation guidelines applied to all states
global_action_guidelinesYesAction guidelines applied to all states
global_boundary_constraintsYesBoundary constraints applied to all states
statesYesArray of state definitions (action, decision, recall, annotation, reflection, or tool-call)
org_idNoOrg ID (uses active org if omitted)
Behavior2/5

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

With no annotations, the description must convey behavioral traits. It mentions version creation and a constraint on terminal state, but lacks details on side effects, authentication needs, rate limits, or what happens to existing versions. The description is insufficient for safe invocation.

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 extremely concise with two sentences, front-loading the core purpose and a key constraint. There is no superfluous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high complexity (11 parameters, nested objects, no output schema), the description is far from complete. It does not explain what a 'context graph' is, what 'creating a new version' entails, or what the tool returns. The agent lacks sufficient context to use it properly.

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 coverage is 100%, so the schema already documents parameters. The description adds a validation rule not in the schema (terminal state must have exactly one action), providing some extra value, but most parameter meaning is already covered by schema 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?

The description clearly states it updates a context graph by creating a new version, with a specific verb and resource. It is implicitly distinct from the sibling 'forge_context_graph_create' tool, but does not explicitly differentiate from other sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, such as 'forge_context_graph_create'. It does not specify prerequisites, when not to use it, or any post-conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/amigo-ai/forge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server