Skip to main content
Glama
efranceschetti

festo-codesys-mcp

PLC Quick Lookup

plc_lookup
Read-onlyIdempotent

Quickly decode PLC prefixes, state numbers, and error codes. Get instant answers for naming conventions and error diagnostics.

Instructions

Quick lookup for PLC conventions and error codes — instant answers without loading full knowledge topics. USE WHEN: you need a single fact — prefix, state number, error code — without loading a full topic. Try this BEFORE plc_knowledge for point lookups. Actions: 'hungarian' (type→prefix), 'type_prefix' (POU→prefix), 'state' (state number→name), 'error_code' (decode Festo/CiA402/CODESYS error), 'fb_interface' (standard FB pattern), 'list_standard' (full reference).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueNoThe value to look up (type name, POU type, state number, or error code)
actionYes'hungarian': get prefix for a type | 'type_prefix': get prefix for POU type | 'state': decode state number | 'error_code': decode error | 'fb_interface': show standard FB pattern | 'list_standard': full convention reference

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
foundYes
actionYes
detailsYes
messageYes
Behavior4/5

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

The description adds context beyond annotations by noting 'instant answers without loading full knowledge topics', which implies no side effects and fast response. Annotations already indicate readOnly, idempotent, non-destructive behavior, and the description complements this well without contradiction.

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 concise, well-structured with a clear 'USE WHEN' block and action list. Every sentence adds value, and it is front-loaded with the tool's purpose.

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?

Given the output schema exists, the description does not need to detail return values. It covers usage context and actions comprehensively. Minor gap: no mention of error handling for invalid lookup values.

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 100%, so the schema already documents both parameters well. The description lists actions but does not add significant new meaning beyond what is in the schema's parameter descriptions.

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 clearly states the tool's purpose: quick lookup for PLC conventions and error codes. It lists specific actions, which helps distinguish from siblings, though it does not explicitly differentiate from all listed sibling tools.

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

Usage Guidelines4/5

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

The description provides clear usage guidance: 'USE WHEN: you need a single fact' and suggests trying this tool before a related tool (plc_knowledge) for point lookups. However, it does not mention when not to use it relative to the listed sibling tools.

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/efranceschetti/festo-codesys-mcp'

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