Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Shared Services

list_shared_services
Read-onlyIdempotent

Retrieves shared services from the IPEX API, optionally filtered by customer ID, so assistants can review which services are shared across accounts.

Instructions

List of shared services. IPEX API: GET /v1/services/shared.

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

Input Schema

NameRequiredDescriptionDefault
customerIdNoQuery parameter 'customerId' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description. The description adds only the underlying IPEX endpoint mapping, which is mildly useful for traceability but reveals nothing about filtering behavior, result size, or pagination.

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 with the purpose front-loaded and no padding. The endpoint reference is arguably low-value but is at least compact and placed after the purpose.

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

Completeness3/5

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

For a simple, no-required-parameter read-only list with full annotations and full schema coverage, the definition is minimally adequate. It still leaves the agent guessing what a "shared service" contains and whether results are paginated, since no output schema exists to answer that.

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 coverage is 100% for the single optional customerId parameter, so the schema carries the burden and the baseline of 3 applies. The description does not explain what customerId scopes (e.g., whether null returns all customers), adding no meaning 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?

The description states a verb ("List") and a resource ("shared services"), which is enough to grasp the basic operation, but it never distinguishes this from the sibling list_services or explains what "shared" scopes to. It is a thin restatement of the tool title.

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 prerequisites, and no pointer to an alternative such as list_services. The only added content is the backend endpoint reference, which tells an agent nothing about which tool to pick.

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