Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

Check developer key

sdk_key_check
Read-onlyIdempotent

Validates a Connect IQ developer key by checking PKCS#8 DER format, RSA size, file permissions, and SHA-256 public-key fingerprint, returning metadata only and never key bytes.

Instructions

Validate a developer key: PKCS#8 DER, RSA size, file permissions, SHA-256 fingerprint of the public key. Never returns key bytes.

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_key_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNodeveloper key (.der) inside the root (default: CIQ_MCP_KEY)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the description's added value is the explicit 'Never returns key bytes' guarantee, which is meaningful security context for a tool touching private key material. It also discloses the checks performed, though it does not say whether failures raise errors or return a report.

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?

Two short, dense sentences with the enumeration of checks front-loaded and the key non-return guarantee placed at the end for emphasis. Nothing is wasted, though the fragment-style list reads slightly telegraphic.

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, read-only, closed-world tool this covers purpose, checks, and the sensitive-data guarantee. With no output schema, it could still say what a successful check returns (fingerprint value, boolean, report shape) to fully close the loop.

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 path parameter is already documented in the schema, including its default. The description adds no further detail about path resolution or what happens when the parameter is omitted, so the baseline of 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?

States a specific verb (validate) and resource (developer key), then enumerates exactly what is validated: PKCS#8 DER format, RSA size, file permissions, and SHA-256 fingerprint. This makes it clearly distinct from the sibling sdk_key_generate, which produces rather than inspects a key.

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 is only implied by the verb 'validate' - an agent can infer this is a pre-flight or diagnostic check on an existing key file, but the description never says when to call it (e.g., before sdk_build) or when not to. No alternative is named or excluded.

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