Skip to main content
Glama

Store: Recommend Apps

recommend_apps_to_install
Read-onlyIdempotent

[Plugins] [What it does] Recommends every visible sales-channel or supplier-platform application of the selected type that is not yet installed; read-only. [When to use] Use when the user wants to discover another channel or supplier platform. [When not to use] To install and authorize a selected sales-channel application, use start_store_connection; to inspect connected stores, use list_stores. [How to use] Set app_type to seller, supplier, or all (the default). The Tool does not provide keyword filtering or caller-controlled pagination. An empty recommendation list is valid. [Side effects] Read-only; installs or authorizes nothing. [Confirmation] No confirmation required. [Follow-up] If the user selects a channel application, continue with start_store_connection; otherwise report the recommendations or empty result and stop.

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

Input Schema

NameRequiredDescriptionDefault
app_typeNoApplication type to recommend: all, seller (sales channels), or supplier (platforms).all

Output Schema

NameRequiredDescriptionDefault
recommendationsYesVisible online applications that are not installed
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description still adds real behavior: no keyword filtering, no caller-controlled pagination, an empty result is valid, and nothing is installed or authorized. It also states no confirmation is required, which matters for an agent deciding whether to ask the user first.

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?

The labeled blocks are front-loaded and scannable, with purpose, usage, exclusions, and side effects in a predictable order. The bracketed headings are slightly heavier than prose would be, but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 discovery tool with an output schema that already documents return values, the description covers everything an agent needs: what is returned, what is excluded, what an empty result means, and where to go next.

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 enum parameter already documents all, seller (sales channels), and supplier (platforms), including the default. The description restates the same three values without adding syntax or edge-case behavior for the parameter, so it meets but does not exceed the baseline.

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?

The description names a specific verb and resource (recommend visible sales-channel or supplier-platform applications) and adds a precise scope qualifier: only those not yet installed. It is immediately distinguishable from siblings like start_store_connection and list_stores, which are named in the same definition.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use (user wants to discover another channel or supplier platform) and when-not-to-use with the exact alternative for each case: start_store_connection for installing/authorizing and list_stores for inspecting connected stores. The follow-up section restates the branch point after a selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.