Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

Generate developer key

sdk_key_generate

Generates an RSA-4096 DER developer key only for a new Connect IQ app; requires a gitignored path inside the repo root and refuses to overwrite.

Instructions

Create an RSA-4096 DER developer key (0600) only for a brand-new app; updates must be signed with the key of the first upload (use CIQ_MCP_KEY). In a git repo the path must be gitignored. Never overwrites. Back it up.

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": {
      "path": "<path>"
    },
    "name": "sdk_key_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesnew key file inside the root and ignored by git, e.g. keys/developer_key.der

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond annotations, it discloses key format and permissions (RSA-4096 DER, 0600), overwrite behavior (never overwrites), gitignore requirements, and a backup warning. These details materially help an agent avoid unsafe or invalid key generation.

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 dense and front-loaded: creation constraints, update exclusion, gitignore rule, overwrite behavior, and backup advice all appear without filler. Every sentence carries operational value.

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 one-parameter key-generation tool, it covers the important safety and scoping constraints and aligns with annotations that already mark it as non-read-only, non-idempotent, and non-destructive. It does not describe the return behavior, which is a modest gap given that there is no output schema.

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%, and the schema already explains that path must be a new key file inside the root and ignored by git. The description reinforces the gitignore constraint but adds no path syntax or format detail 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?

It states a specific verb and resource: create an RSA-4096 DER developer key, with the 0600 permission detail. It also distinguishes the legitimate case (a brand-new app) from the excluded case (updates), which sharply separates it from key-checking or build siblings.

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?

It gives explicit when-to-use guidance: only for a brand-new app. It also gives an explicit when-not and workaround for updates, directing the agent to sign with the first upload's key via CIQ_MCP_KEY.

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