WinProLadder MCP

Overview Schema Source Related Servers Discussions Admin

get_instruction_capabilities

Read-only

List instruction families or get limits and evidence for a selected family to verify supported FATEK ladder-logic instructions.

Instructions

List instruction families, or get limits and evidence for one selected family.

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": "get_instruction_capabilities"
  }
}

Input Schema

Name	Required	Description	Default
`family`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.1.0Nov 6, 2026
- addedInput schema / properties / family / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / family / default
```
Added value: +null
```
- removedInput schema / properties / family / type
```
Removed value: -"string"
```
- removedInput schema / required
```
Removed value: -[
-  "family"
-]
```
Addedv1.0.0Oct 28, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare this is a read-only, non-destructive, closed-world operation. The description adds the dual-mode behavior, but 'limits and evidence' is never explained, so the agent cannot anticipate the kind of data returned or its scope.

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?

A single well-formed sentence with the list behavior front-loaded and the detail behavior second. No padding, though the compression leaves key terms undefined.

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

Completeness3/5

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

An output schema exists, so return structure need not be described. Still, for a tool whose only parameter has zero schema documentation and whose 'evidence' output is undefined, an agent might call this without understanding what it will receive or how to name a family.

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

Parameters3/5

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

Schema coverage is 0%, so the description carries the burden. It does say the family parameter selects a single family for detail retrieval, which is real added meaning, but it never says what a valid value looks like (name, ID, exact string) or whether unknown values error out.

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?

The description names a concrete resource (instruction families) and two modes: listing all families, or retrieving limits and evidence for one selected family. This distinguishes it from most siblings, though it does not differentiate from the similarly named get_capabilities.

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 'or' clause implies the selection rule (omit family to list, supply family to get details), which is useful implicit guidance. However, no explicit when-to-use/when-not-to-use statement or alternative tool is named.

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