Skip to main content
Glama
Sign In
FlexSim MCP Server

FlexSim MCP Server

by fateedit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

list_instances

Lists all running model instances on the WebServer, including model name and instance number, so you can confirm the target model is online before operating.

Instructions

列出 WebServer 上所有运行中的模型实例（模型名+实例号）。操作前先调用确认目标模型在线。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_instances"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the key behavioral trait that only running instances are returned and that the call is a prerequisite check, but says nothing about failure behavior when the WebServer is not running (relevant given siblings webserver_status and start_webserver) or about read-only semantics.

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?

Two short sentences, zero filler, with the scope ('all running instances') front-loaded before the usage instruction. Every clause carries information.

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 simple zero-parameter read tool this is close to complete: it says what is listed and what is returned. The only material gap is the precondition that the WebServer must be up, which the agent must infer from the sibling tools.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to clarify. It does add value by describing the result content (model name + instance number), which partially compensates for the missing output schema.

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?

States a specific verb+resource (list all running model instances on the WebServer) and even previews the returned fields (model name + instance number). This distinguishes it from the sibling list_models, which lists model definitions rather than live instances, though the description never names that sibling explicitly.

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?

Explicitly instructs to call this before other operations in order to confirm the target model is online, giving a clear triggering context. It does not state when NOT to use it or contrast it with list_models / get_run_state, so alternatives remain implicit.

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

Deploy Server

Other Tools