Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

Connect IQ SDK info

sdk_info
Read-onlyIdempotent

Inspect installed Connect IQ SDKs and show the active version, selection source, Java setup, data root, and device count; pass an installed SDK version to target it.

Instructions

Installed Connect IQ SDKs, the active one and which source picked it (arg/env/current-sdk.cfg/newest), Java, data root and device count.

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

Input Schema

NameRequiredDescriptionDefault
sdkNoinstalled SDK version or dir name, e.g. 9.2.0; a custom SDK only via CIQ_MCP_SDK

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious detail by disclosing that the active SDK comes with its resolution source (arg/env/current-sdk.cfg/newest), but it says nothing about behavior when no SDK is installed or what an unknown sdk value yields.

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?

One dense sentence with zero filler, and the core resource is front-loaded. It reads as a telegraphic field list rather than prose, but every clause carries information.

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 simple read-only info tool with one optional param and no output schema, listing the returned facets largely substitutes for an output schema. Only error/empty-state behavior is left uncovered.

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% and the single optional 'sdk' parameter is fully documented in the schema, including the CIQ_MCP_SDK custom-SDK constraint. The description adds no parameter semantics, which is the expected baseline here.

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?

Names the specific resource ('Installed Connect IQ SDKs') and enumerates the reported facets: active SDK, the source that selected it (arg/env/current-sdk.cfg/newest), Java, data root, device count. This is clearly distinct from siblings like sdk_build or sdk_devices_list, though the verb is implied rather than stated.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no named alternative. An agent can infer that this is the discovery/status call to run before sdk_build, but the description never says so.

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