mcp-server

list_order_channels

Read-onlyIdempotent

List the marketplaces that can be added as a standalone ORDER connection — order-capable channels that do NOT have a product wizard. Use this when the user wants to add a standalone order connection. (Channels that DO have a wizard are added with create_marketplace instead, not here.) Returns {channels:[{channelApiCode, label, channelCode, logoUrl, authType ('oauth'|'api_key'), available}], total}. 'available' is false when the project already has as many order connections as this Koongo account includes; get_order_connection_setup_link makes the final check. Pass a channelApiCode to get_order_connection_setup_link to start adding one. Optional query filters by name/code. project_id is OPTIONAL (inferred for a single-project customer; project_id_required otherwise — then call list_projects).

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

Input Schema

Name	Required	Description	Default
`query`	No	Optional filter on channel name/code.
`project_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it explains the meaning of the 'available' flag (account connection limit reached) and warns that get_order_connection_setup_link makes the final check. It also discloses the project_id inference/error path (project_id_required, then call list_projects), which is real behavioral context an agent needs.

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?

Purpose is front-loaded in the first clause and no sentence is filler, but the paragraph is dense with nested parentheses and quoted literals, making it harder to scan than a short bulleted breakdown would be. Still efficient for the amount of information conveyed.

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?

There is no output schema, yet the description spells out the return shape (channels array with channelApiCode, label, channelCode, logoUrl, authType, available, plus total). Combined with the workflow routing and limit semantics, an agent has everything needed to call and interpret it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% (project_id has no schema description), but the description compensates fully: project_id is optional, inferred for single-project customers, and required/error-triggering otherwise. The query filter's behavior (name/code) is also restated consistently with the schema.

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?

States a specific verb and resource (list order-capable channels addable as standalone ORDER connections) and immediately narrows the scope with 'do NOT have a product wizard'. This lets an agent distinguish it from list_marketplace_channels and create_marketplace without opening any schema.

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?

Explicitly says when to use it ('user wants to add a standalone order connection') and when not to, naming the alternative tool for wizard-based channels: create_marketplace. It also gives the next step in the workflow by directing the agent to pass a channelApiCode to get_order_connection_setup_link.

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

All mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?