Skip to content

refactor: rename "agent" to "server" throughout workflow/ (#170)#218

Merged
DhavalRepo18 merged 3 commits intomainfrom
refactor/issue-170-rename-agent-to-server
Mar 19, 2026
Merged

refactor: rename "agent" to "server" throughout workflow/ (#170)#218
DhavalRepo18 merged 3 commits intomainfrom
refactor/issue-170-rename-agent-to-server

Conversation

@ShuxinLin
Copy link
Collaborator

$(cat <<'EOF'

Summary

Closes #170.

Renames all agent terminology to server in src/workflow/ to align with MCP architecture — servers expose tools, the plan-execute runner is the agent.

  • PlanStep.agentPlanStep.server, StepResult.agentStepResult.server (models.py)
  • _AGENT_RE_SERVER_RE, agent_descriptionsserver_descriptions, prompt strings #Agent<N>:#Server<N>:, "assign an agent" → "assign a server", "Agent and tool names" → "Server and tool names" (planner.py)
  • get_agent_descriptions()get_server_descriptions(), error messages updated (executor.py)
  • agent_descriptionsserver_descriptions, log strings updated (runner.py)
  • step.agent / r.agent field accesses updated (cli.py)
  • All test fixtures, plan strings, and assertions updated (tests/)

Out of scope: FastMCP server display names (IoTAgent, FMSRAgent, TSFMAgent) — those are public-facing MCP client identifiers tracked separately.

Test plan

  • All 58 workflow unit tests pass (uv run pytest src/workflow/tests/ -v)
    EOF
    )

Replace all uses of "agent" terminology with "server" in models, planner,
executor, runner, CLI, and tests to match MCP architecture where servers
expose tools and the plan-execute runner is the actual agent.

Signed-off-by: Shuxin Lin <linshuhsin@gmail.com>
IoTAgent → iot, FMSRAgent → fmsr, TSFMAgent → tsfm,
WorkOrderAgent → wo, Utilities → utilities.

Updates FastMCP() names in all server main.py files, DEFAULT_SERVER_PATHS
keys in executor.py, all test fixtures and plan strings, and INSTRUCTIONS.md.

Signed-off-by: Shuxin Lin <linshuhsin@gmail.com>
When execute_step encounters a tool=none step that has prior-step
dependencies, it was returning the static expected_output description
instead of deriving the actual value from the dependency context.
Downstream steps depending on that result would receive the description
string (e.g. "The name and id of a chiller asset...") and fail to
resolve their {step_N} placeholders correctly.

Fix: for tool=none steps with dependencies present in context, call the
LLM with a short extraction prompt to derive the concrete value.  Steps
with no dependencies retain the previous behaviour (return expected_output).

Signed-off-by: Shuxin Lin <linshuhsin@gmail.com>
Copy link
Collaborator

@DhavalRepo18 DhavalRepo18 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a cosmetic change to adjust the teminomogy.

@DhavalRepo18 DhavalRepo18 merged commit 54696dd into main Mar 19, 2026
1 check passed
@DhavalRepo18 DhavalRepo18 deleted the refactor/issue-170-rename-agent-to-server branch March 19, 2026 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

refactor: rename "agent" terminology to "server" throughout mcp/plan_execute/

2 participants