Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

Reference lists

store_references
Read-onlyIdempotent

Fetch reference lists for Connect IQ Store languages and locale codes, categories by app type, and countries to populate accurate listings and forms.

Instructions

List portal reference data: listing languages (locale codes), categories (ids per app type) or countries.

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": {
      "type": "<type>"
    },
    "name": "store_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesreference list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the safety and repeatability profile is covered structurally. The description adds the useful detail that this is reference/lookup data and tells what each list contains (locale codes, ids per app type, countries). It does not disclose whether the data is static or cached, how large the lists are, or their shape, which would have raised the score with no output schema present.

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 front-loaded sentence that states the resource, then immediately maps each option to its content. No filler, no redundancy, nothing to trim.

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 lookup tool with full schema coverage and safety annotations, the description supplies what an agent needs to pick the right enum value. The only shortfall is that no output schema exists and the description gives no hint of the returned structure beyond 'locale codes' and 'ids'.

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% and the single enum already lists languages/categories/countries, so the baseline would be 3. The description goes beyond the schema by explaining that 'languages' yields locale codes and 'categories' yields ids per app type, which is genuine semantic value about what each enum selection actually returns.

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?

The description uses a specific verb (List) and resource (portal reference data), then enumerates the three enumerable lists. It is easy to separate from siblings such as store_apps_list or store_reviews_list because it clearly deals with static lookup tables rather than app/review data, though it never explicitly names a sibling to contrast with.

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: an agent can infer this is the tool to call to resolve valid locale codes, category ids, or country values before invoking other tools. There is no explicit when-to-use, when-not-to-use, or prerequisite guidance. Adequate but leaves the agent to reason about the call site.

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