@inscada/mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

inscada_api_endpoints

Read-only

Search and filter inSCADA REST API endpoints by keyword, category, or HTTP method to discover 625 available endpoints for integration.

Instructions

Discover inSCADA REST API endpoints. Search/filter among 625 endpoints by keyword, category, or HTTP method.

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

Input Schema

Name	Required	Description
`search`	No	Search term (searches in path, summary, tag). E.g. 'alarm group', 'trend', 'report'
`category`	No	Category filter: alarms, variables, connections, scripts, projects, reports, visualization, trends, users, spaces, menus, expressions, data-transfer, custom, protocols, templates, system, other
`method`	No	HTTP method filter
`tag`	No	OpenAPI tag filter (controller name). E.g. 'alarm-group', 'trend-controller'
`limit`	No	Max results (default: 30, max: 50)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.7.1May 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating safe read-only behavior. The description adds no additional behavioral traits beyond confirming the search/discovery nature. No contradiction with annotations.

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, front-loaded sentence that conveys the core purpose and scope (625 endpoints) without any wasted words. Every part is essential.

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?

With 5 parameters fully described in the schema, annotations present, and no output schema needed, the description provides sufficient context for a search tool. It could include a brief example of usage, but the schema's description for the search parameter includes examples. Overall complete for its complexity.

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 description coverage is 100%, so the schema fully documents all 5 parameters. The description mentions searching by keyword, category, or HTTP method, but this adds minimal value beyond the schema's parameter descriptions. Baseline 3 applies.

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 'Discover inSCADA REST API endpoints. Search/filter among 625 endpoints by keyword, category, or HTTP method.' It clearly identifies the tool's purpose as discovery and search, distinguishing it from sibling tools that perform specific operations (e.g., list_variables, get_script).

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 when to use the tool (when searching or filtering endpoints) but does not explicitly state when not to use it or mention alternatives among the many sibling tools. No usage guidance beyond the basic purpose.

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