Skip to main content
Glama
Edge-JB

te1000-mcp

by Edge-JB
OverviewSchemaRelated ServersScoreDiscussions
Local

tc_link

Create, remove, resolve, and list variable links between PLC producers and consumers. Batch operations handle multiple links in a single request with failure-only roll-up.

Instructions

Variable links (producer↔consumer); dot-form PLC subfields auto-resolve to XAE ^ subitem form. BATCH-FIRST: for more than one link use link_batch/unlink_batch — N ops in ONE DTE attach, failures-only roll-up by default ({count,succeeded,failed}; details:true for every row incl. resolved paths), instead of an attach per link. Actions, grouped single / batch: LINK — link (a=source, b=destination) / link_batch (links:[{a,b}]); UNLINK — unlink (a, optional b; a alone removes all its links) / unlink_batch (links:[{a,b?}]); resolve (report valid path forms for a — compact {originalPath,resolvedPath,resolved} on success; verbose:true for the attempts[] permutation list); links (a=item path; reports that item's current variable links — closes the discover→act→verify loop). link/resolve drop resolution detail by default — verbose:true restores it. Mutating batch verbs accept save:true to save once after the batch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYes
bNo
saveNo
linksNo
actionYes
detailsNolink_batch/unlink_batch: include ok:true rows (with resolved paths); default failures-only
verboseNolink/resolve: return the full resolution detail (producerResolution/consumerResolution or attempts[]); default compact
autoResolveNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv2.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changedv2.3.0
    • addedInput schema / properties / details
      Added value: +{
+  "description": "link_batch/unlink_batch: include ok:true rows (with resolved paths); default failures-only",
+  "type": "boolean"
+}
    • addedInput schema / properties / verbose
      Added value: +{
+  "description": "link/resolve: return the full resolution detail (producerResolution/consumerResolution or attempts[]); default compact",
+  "type": "boolean"
+}
  3. Changed3 schema fields changedv2.1.1
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "link",
-  "unlink",
-  "resolve"
-]New value: +[
+  "link",
+  "unlink",
+  "resolve",
+  "link_batch",
+  "unlink_batch",
+  "links"
+]
    • addedInput schema / properties / links
      Added value: +{
+  "items": {
+    "properties": {
+      "a": {
+        "type": "string"
+      },
+      "b": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "a"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / save
      Added value: +{
+  "type": "boolean"
+}
  4. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations exist, so the description must fully disclose behavior. It covers some aspects: mutation with save:true, read-only 'resolve' and 'links' actions, default roll-up for batches, and compact output. However, it omits permission requirements, idempotency, side effects, and error handling details. The transparency is adequate but incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph that contains all necessary information but lacks bullet points, section headers, or clear organization. Front-loading is present first sentence states purpose but the text becomes overwhelming with technical specifics, making it less efficient for an AI agent to parse.

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 tool with 8 parameters and no output schema, the description covers the main use cases, parameter interactions, and optimization advice (batch-first). It explains resolve return format and links action behavior. However, it does not specify return values for link/unlink actions and leaves the autoResolve parameter unexplained. The description is mostly complete for basic operations.

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 description coverage is only 25%, but the description compensates by attributing meanings to most parameters: a=source, b=destination, links=[{a,b}], action enum, details for full rows, verbose for resolution detail. The autoResolve parameter is not explicitly described, and some parameter behavior (optional b for unlink) is only implicitly stated. Overall, the description adds significant value beyond the schema.

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 explicitly states that the tool manages variable links (producer↔consumer) and provides a clear list of actions (link, unlink, resolve, links, and batch variants). It distinguishes the batch versions as BATCH-FIRST for multiple links, making the core purpose unambiguous despite technical jargon.

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?

The description gives explicit guidance on when to use batch verbs ('for more than one link use link_batch/unlink_batch') and explains default behaviors (failures-only roll-up, compact vs verbose output). It also clarifies optional flags (details, verbose, save) across actions, providing context for selecting the right approach.

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/Edge-JB/TwinCAT-XAE-MCP'

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