Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Connectors

list_connectors
Read-onlyIdempotent

List IPEX connectors, optionally filtered by type, customer ID, connector ID, or price display, to review or find B2B connectors for a customer.

Instructions

List of all connectors. IPEX API: GET /v1/connectors.

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_connectors"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoQuery parameter 'type' of the IPEX API.
showPriceNoQuery parameter 'showPrice' of the IPEX API.
customerIdNoQuery parameter 'customerId' of the IPEX API.
connectorIdNoQuery parameter 'connectorId' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond the safety profile: no pagination or result-size behavior, no auth requirements, no note on what the filters do or whether the list is truncated. Only the raw endpoint (GET /v1/connectors) is supplied, which does not help an agent behave correctly.

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?

Two short sentences, front-loaded with the operation and free of padding. The trailing "IPEX API: GET /v1/connectors" is of marginal value for tool selection but costs almost nothing.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a list tool with four optional filters and no output schema, so the description should explain what a connector is, what the filters narrow, and what the response looks like. None of that is present; the definition is far too thin for the tool's practical complexity.

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 nominally 100%, so the baseline is 3. In practice the schema text is pure boilerplate ("Query parameter 'type' of the IPEX API"), and the description adds no meaning for type, showPrice, customerId or connectorId, so the agent cannot tell which filter to use for which intent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List of all connectors" names an unambiguous verb and resource and signals unfiltered scope with "all", so an agent knows what comes back. However, it effectively restates the tool name and title and gives no basis for distinguishing it from the many other list_* siblings, leaving it at minimum-viable clarity.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives such as list_containers or list_customers, and no statement of prerequisites or when the optional filters should be applied. The agent must infer everything about selection from the name alone.

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

Deploy Server

Other Tools