Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

Read manifest.xml

sdk_manifest_get
Read-onlyIdempotent

Parses a Connect IQ manifest.xml to extract app ID, type, minimum API level, products, permissions, and languages, and flags products not installed locally.

Instructions

Parse a project's manifest.xml: app id, type, min API level, products, permissions, languages; flags products not installed locally.

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

Input Schema

NameRequiredDescriptionDefault
pathNomanifest.xml or project dir inside the root (default: root)

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 already cover readOnly, idempotent, and closed-world, so the bar is lower; the description still adds value by disclosing the returned contents and the derived 'not installed locally' flag. It omits what happens when no manifest exists at the given path, which is the main remaining gap.

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?

One densely packed sentence, front-loaded with the verb and resource, followed by a semicolon-separated field list. No filler and nothing buried.

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 tool with no output schema, enumerating the extracted fields effectively substitutes for a return-value description, which is the key completeness requirement here. Only the error behavior for a missing or invalid manifest is unaddressed.

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?

The single optional 'path' parameter is fully documented in the schema, including its default of the project root, and the description adds nothing about it. With 100% schema coverage the schema does the work, so the baseline 3 applies.

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?

States a specific verb (parse) and resource (manifest.xml), then enumerates exactly what it extracts: app id, type, min API level, products, permissions, languages. This makes it clearly a read operation distinct from the sibling setter sdk_manifest_set_products, though it never names any sibling explicitly.

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: the phrase 'flags products not installed locally' hints at inspecting install state, and the read-only nature suggests it precedes a set_products call, but there is no explicit when-to-use or when-not-to-use statement.

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