Skip to main content
Glama
Razee4315

NetLogo MCP

by Razee4315
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

open_comses_model

Download or load a COMSES model from cache, resolve version, and open it in NetLogo workspace if compatible, or return structured metadata for other models.

Instructions

Download (or reuse cache), then open a COMSES model ready to use.

This is the single entry point most AI flows should call.

Behavior:

  • Resolves "latest" to a concrete version BEFORE any cache path is computed. The returned resolved_version is what every follow-up read_comses_files call MUST pass — never re-pass "latest" in the same flow, or you risk inspecting a different cache slot than the model you just loaded.

  • If the cache for (identifier, resolved_version) is already complete (has .comses_complete), skips download.

  • Otherwise, downloads + extracts safely (same logic as download_comses_model).

  • If the model is NetLogo, picks one .nlogo / .nlogox per Section 4.4 rules (exactly one → use it; else prefer code/; else prefer .nlogox; else lex-largest relative path — a deterministic tie-breaker, NOT semver-aware).

  • If NetLogo, loads it into the workspace.

  • If not NetLogo, returns structured info for manual follow-up.

Returns JSON with:

  • status: "loaded_netlogo", "not_runnable_in_netlogo", or "no_netlogo_file".

  • resolved_version: concrete version string (never "latest").

  • identifier, title, language, license, cached.

  • extracted_path: absolute path to cached model directory.

  • all_netlogo_files: list of every NetLogo file found.

  • loaded_netlogo_file: the one selected (if any).

  • code_files: source files by extension.

  • odd_doc: ODD / README path, if any.

  • message: short text for the AI to show the user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_mbNoMax download size in MB. Pass 0 or omit to use the env default.
versionNoVersion string or "latest".latest
identifierYesFull model UUID.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Despite no annotations, the description fully discloses caching, version resolution, NetLogo file selection rules, and the exact return format with all fields. No surprises.

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?

Well-structured with bullet points and clear sections. Though lengthy, every sentence adds necessary detail about behavior and return fields. Minimal redundancy.

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

Completeness5/5

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

Given the presence of an output schema in the description and many sibling tools, the description covers caching, version resolution, NetLogo selection, return JSON fields, and error states (no_netlogo_file). Complete for the tool's complexity.

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 100%, but description adds value by explaining version resolution ('latest' to concrete), max_mb default behavior, and identifier as UUID. Slightly above baseline 3.

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 clearly states the tool downloads/opens a COMSES model, says it's the 'single entry point', and distinguishes itself from siblings like read_comses_files and download_comses_model by detailing its unique behavior.

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

Usage Guidelines5/5

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

Explicitly states when to use ('single entry point most AI flows should call'), provides specific guidance on not re-passing 'latest' in the same flow, and mentions follow-up tool (read_comses_files).

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/Razee4315/NetLogo-MCP'

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