Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Connector

get_connector
Read-onlyIdempotent

Retrieves the details of a specific IPEX connector by its connectorId via GET /v1/connectors/{connectorId}. Use it to look up configuration and status data for one B2B connector.

Instructions

Connector detail. IPEX API: GET /v1/connectors/{connectorId}.

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": {
      "connectorId": "<connectorId>"
    },
    "name": "get_connector"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectorIdYesPath parameter 'connectorId' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only that this is a direct IPEX GET passthrough for a single connector, which is modest added context; it says nothing about error behavior, permissions, or what the returned detail contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two fragments, no wasted words, and the resource is front-loaded, but the telegraphic style ('Connector detail.') reads as an under-specified note rather than a purposeful statement of what the tool returns.

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?

For a single-lookup tool with one parameter and no output schema, the description should at least hint at what a connector record contains or what the call returns. Instead it gives only an endpoint reference, leaving the agent without a picture of the response.

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 connectorId parameter is already documented as the IPEX path parameter. The description merely restates the endpoint template, adding no format, sourcing, or validation details beyond the schema.

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?

"Connector detail" plus the raw endpoint signals a single-record fetch of a connector, so the resource is identifiable, but there is no explicit verb and nothing distinguishes it from connector-related siblings such as get_connector_analysis or list_connector_phone_numbers beyond the generic name.

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?

No when-to-use guidance, no prerequisites, and no mention of when a sibling (e.g. the analysis or phone-number variants) would be a better choice. The agent must infer usage purely from the tool name.

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