Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

Toolsets

toolsets

Manage Connect IQ MCP tool groups for the current session: list, enable, or disable groups, refresh available tools, and request user approval for write actions.

Instructions

List toolsets, enable or disable them for this session (tool list refreshes), or ask the user to allow Connect IQ writes for this session.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "toolsets"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYeswhat to do
toolsetsNotoolsets for enable/disable

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare this is a non-read-only, non-idempotent, non-destructive operation, and the description adds real context beyond that: the change is scoped 'for this session', enabling/disabling triggers a tool list refresh, and enable_writes involves asking the user. What remains unsaid is whether session changes are reversible or persist after the session, though 'for this session' strongly implies they do not.

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 front-loaded sentence packs the three modes in the order they matter, with no filler. It is dense but readable; slight density cost keeps it from a 5.

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 two-parameter enum-driven session tool, the description covers all action modes, the session lifetime of changes, the refresh side effect, and the user-facing permission prompt. The only gap is what a 'list' returns, which is minor given there is no output schema and the result is self-evident.

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 coverage is 100%, so the baseline is 3. The description earns above baseline by spelling out the meaning of each action value (list / enable or disable / request Connect IQ writes), which the schema only labels 'what to do', and by clarifying that the toolsets array applies specifically to the enable/disable case.

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 concrete verbs and the resource: list toolsets, enable/disable them, and request Connect IQ write permission. An agent can map each of the three modes to the action enum without ambiguity. It does not differentiate itself from siblings like auth_status, but its session-configuration scope is distinct enough from the sdk_*/store_* names to be recognizable.

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?

Usage context is implied by the description ('for this session', 'ask the user to allow Connect IQ writes'), which tells the agent that enable_writes is a permission-request flow rather than a plain toggle. However, it never states when an agent should enable or disable a toolset, nor any precondition for listing before mutating. Guidance exists but requires inference.

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