Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

List store apps

store_apps_list
Read-onlyIdempotent

Lists Connect IQ store apps for the signed-in developer, returning UUID, title, status, type, manifest ID, current version, and rating when available.

Instructions

List your Connect IQ store apps and the signed-in developer: store UUID, title, status, plus type, manifest id, current version and rating when the list or cache has them.

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": "store_apps_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral hint — fields appear only "when the list or cache has them", signalling possible cache staleness or partial data — but it says nothing about result size, ordering, or pagination for a network-backed listing.

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 sentence, front-loaded with the action and resource, with the field list following as supporting detail. The trailing qualifier "when the list or cache has them" is slightly awkward but carries real meaning and earns its place.

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 carries the burden of describing returns, and it does list the concrete fields an agent will get plus the caveat that they may be absent. The remaining gap is scope (full list vs. a page, and whether results are capped) for an openWorld network call.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly does not fabricate parameter guidance for a schema that has none.

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?

Uses a clear verb+resource pair ("List your Connect IQ store apps and the signed-in developer") and enumerates the returned fields (store UUID, title, status, type, manifest id, version, rating). It is distinguishable from singular siblings like store_app_get and from store_reviews_list by scoping to apps plus developer identity, though it never explicitly contrasts itself with those siblings.

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: an agent can infer this is the broad listing call that precedes drilling into a single app. There is no explicit statement of when to prefer store_app_get, whether the result is the full catalog or paginated, or what prerequisites (auth) apply.

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