Skip to main content
Glama
dnnyngyen
by dnnyngyen

IronManusStateGraph

Isolate state per project for managing sessions, phases, and tasks using a knowledge graph. Create entities, transitions, and track task status for workflow orchestration.

Instructions

Project-scoped FSM state management using knowledge graphs. Manage sessions, phases, tasks, and transitions with isolated state per project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoDetected role (for initialize_session action)
namesNoEntity names to retrieve (for open_nodes action)
queryNoSearch query (for search_nodes action)
actionYesThe action to perform on the session state graph
statusNoTask status (for update_task_status action)
contentNoTask content (for record_task_creation action)
task_idNoTask identifier (for task operations)
entitiesNoEntities to create (for create_entities action)
priorityNoTask priority (for record_task_creation action)
to_phaseNoTarget phase (for record_phase_transition action)
objectiveNoSession objective (for initialize_session action)
from_phaseNoSource phase (for record_phase_transition action)
session_idYesThe session ID for project-scoped state isolation
transitionsNoState transitions to create (for create_transitions action)
observationsNoObservations to add (for add_observations action)
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It mentions 'FSM state management' and 'isolated state per project' but fails to list supported actions, side effects, or permissions needed. The 15-parameter schema implies complexity not addressed.

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?

The description is concise at two sentences, with no wasted words. However, it lacks structure (e.g., bullet points or sections) that could improve readability for a complex tool.

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

Completeness1/5

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

Given the tool's complexity (15 parameters, 12 actions, no output schema), the description is severely incomplete. It does not explain return values, how actions relate, or typical usage flows, leaving the agent without sufficient context to invoke the tool correctly.

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 baseline is 3. The description does not add any parameter-specific meaning beyond what the schema already provides, thus neither improving nor degrading clarity.

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 that the tool manages project-scoped FSM state using knowledge graphs, specifying it handles sessions, phases, tasks, and transitions. It distinguishes from sibling tools by its domain focus, though it could be more precise about the actions supported.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or scenarios where other tools would be more appropriate.

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/dnnyngyen/iron-manus-mcp'

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