Skip to main content
Glama
Sign In
Vensim MCP

Vensim MCP

by Cybing521
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

render_vensim_preview

Generates an SVG preview from a Vensim model's actual sketch records, using the model path and output path to render the diagram.

Instructions

Render an SVG preview from the model's actual Vensim sketch records.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "model_path": "<model_path>",
      "output_path": "<output_path>"
    },
    "name": "render_vensim_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_pathYes
output_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not state whether rendering writes to output_path, whether existing files are overwritten, whether the operation is read-only, or whether external tools like Vensim are required. Only the primary render action is mentioned.

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 a single sentence with the main verb front-loaded and zero filler. Every word contributes semantic value, making it efficient for an agent to parse quickly.

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?

For a two-parameter tool with no annotations and no output schema, the description is too sparse. The agent cannot determine valid file types for either parameter or fully anticipate the tool's side effects, so calling it correctly would depend on uninformed assumptions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, and the description does not compensate. model_path and output_path are self-explanatory by name, but accepted file formats, expected extensions, and directory constraints are not disclosed anywhere, leaving the agent to guess.

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 states a specific verb ('Render') and resource ('SVG preview'), and specifies the source ('the model's actual Vensim sketch records'). This clearly differentiates it from sibling tools like generate_vensim_model or inspect_vensim_model, which concern creation and inspection rather than visual rendering.

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

Usage Guidelines3/5

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

The description implies a use case: produce a visual preview from the real model sketch. However, it provides no explicit guidance on when to prefer this over inspect_vensim_model or open_vensim_model, nor does it mention any exclusions or prerequisites.

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