Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
rootYesRoot directory for the WinProLadder MCP server

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_capabilitiesA

Get supported operations, instruction/address limits, JSON schema and an example.

inspect_ldrB

Inspect framing, raw bytes, offsets and CRC validity. Read paths are workspace-scoped.

read_ldrB

Read logic in display order; unknown payloads stay opaque. Reject bad CRC.

validate_ladderC

Check IR encoding and report import verification. Not PLC syntax validation.

create_ldrB

Create a new file from IR with sampled header and fresh CRC. Never overwrite files.

simulate_ladderB

Boolean IR scan model, not PLC emulation. Missing X inputs reset false each scan.

Missing initial devices default false. T/C contacts are fixed initial states; timers/counters are not executed. Networks evaluate in display order.

create_start_stopC

Create X0/Y0 self-hold. True: X1=1 stops (verified). False: X1=0 stops (candidate).

export_ldrB

Re-encode to a NEW file, preserving opaque bytes and any original invalid CRC.

modify_networkC

Edit in a NEW file; index 0 is N000. Preserve untouched raw records.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
capability_resource

TDQS

B3.3/5.0

Scored across 9 tools

Disambiguation4/5

Most tools target distinct operations (create, read, modify, simulate, validate, inspect), but create_ldr and export_ldr both produce new files and could be confused, and create_start_stop overlaps in spirit with create_ldr as a specialized generator. inspect_ldr vs validate_ladder vs read_ldr boundaries are reasonably clear from descriptions.

Naming Consistency5/5

Consistent verb_noun snake_case throughout (create_ldr, read_ldr, modify_network, validate_ladder, inspect_ldr). create_start_stop is the only longer form but still follows the same verb-led convention.

Tool Count5/5

Nine tools is well-scoped for a ladder-file manipulation server, spanning creation, reading, editing, export, simulation, inspection, validation, and capabilities discovery without excess.

Completeness4/5

Covers the full lifecycle (create, read, modify, export, validate, simulate) plus a capabilities introspector and a convenience generator. No explicit delete, but the 'never overwrite' design implies deletions are intentionally out of scope.

Maintenance

ActivityMaintained
ResponsivenessNo issues