Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

Get app metadata

store_app_get
Read-onlyIdempotent

Reads an app's Connect IQ store metadata—manifest ID, version, category, compatible devices, screenshots, and per-locale listings—using a UUID, manifest ID, or exact title.

Instructions

Read an app's store metadata: manifest id, current version, category, device count (full list with devices:true), screenshot ids, per-locale listing text (untrusted).

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": {
      "app": "<app>"
    },
    "name": "store_app_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesstore UUID, manifest id, or exact app title
devicesNoinclude the full compatible device list (default: count only)

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 declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral facts: per-locale listing text is untrusted, and the devices flag switches the response from a count to a full device list — a response-shape change the annotations do not convey.

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?

A single dense sentence, front-loaded with the verb and resource, followed by a compact field enumeration. Every clause carries information; nothing is padding.

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?

With no output schema, the description compensates by naming the returned fields, which is exactly what an agent needs to decide between this and sibling getters. Minor gap: no note on error behavior for an unresolvable app, or pagination/size expectations for multi-locale listings.

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 3 baseline applies. The description goes beyond it by explaining the consequence of devices:true (full compatible device list versus count only), which tells the agent the response size/verbosity tradeoff rather than just the type.

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 ('Read') and resource ('app's store metadata') and enumerates the concrete fields returned (manifest id, version, category, device count, screenshot ids, per-locale listings), which separates it from a bulk lister like store_apps_list. It stops short of naming a sibling such as sdk_manifest_get, so the boundary with adjacent getters is left implicit.

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 implied rather than stated: fetch metadata for a single app identified by UUID, manifest id, or exact title. There is no explicit when-to-use/when-not guidance and no signposting to sibling tools for manifest or SDK-level data.

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