Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Connector Analysis

get_connector_analysis
Read-onlyIdempotent

Retrieves connector analysis for a specified period from the IPEX API, with optional end-date filtering, to help review connector performance.

Instructions

Connector analysis. IPEX API: GET /v1/analysis/connector.

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": {
      "periodFrom": "<periodFrom>"
    },
    "name": "get_connector_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodToNoQuery parameter 'periodTo' of the IPEX API.
periodFromYesQuery parameter 'periodFrom' of the IPEX API (required).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructiveness, so safety is covered. The description adds only the upstream endpoint, disclosing nothing about what the analysis returns, whether results are aggregated over the period, or any rate/coverage limits.

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 very short sentences with no padding, and the endpoint reference is secondary. However, its brevity is under-specification rather than economy, and the first sentence merely echoes the name.

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

Completeness1/5

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

There is no output schema, so the description is the only place the return shape could be described, and it says nothing about what the connector analysis contains. For a period-scoped analytical endpoint, the definition is inadequate for correct invocation.

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

Parameters2/5

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

Schema coverage is nominally 100%, but both parameter descriptions are circular ("Query parameter 'periodTo' of the IPEX API"), so neither source explains the date format, acceptable range, or whether periodFrom/periodTo are inclusive. The description adds no meaning at all to the two parameters.

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

Purpose2/5

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

"Connector analysis" restates the tool name and never says what is analyzed or what comes back; the only added detail is the raw upstream route (GET /v1/analysis/connector). An agent cannot tell from this how it differs from get_connector or the connector report siblings.

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

Usage Guidelines1/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 prerequisites, and no mention of any alternative among the many connector/report siblings. The agent is left to infer selection purely from the 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