Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Service

get_service
Read-onlyIdempotent

Retrieves details for a specific IPEX service by serviceId using GET /v1/services/{serviceId}, so assistants can query service data.

Instructions

Get service. IPEX API: GET /v1/services/{serviceId}.

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": {
      "serviceId": "<serviceId>"
    },
    "name": "get_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceIdYesPath parameter 'serviceId' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is fully covered without the description's help. The description adds only the raw REST endpoint mapping, with no note on error behavior (e.g., what happens for an unknown serviceId) or auth requirements.

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 action and the endpoint, with zero filler. The brevity is efficient, though it borders on under-specification rather than tightness.

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 single-parameter read with rich annotations and no output schema, the minimum needed to invoke correctly is present. However, the description never indicates what a 'service' object is or how it differs from the neighboring service-related getters, leaving meaningful ambiguity for an agent selecting among siblings.

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% for the single serviceId parameter, so the schema carries the parameter documentation. The description merely echoes the path template and adds no format, example, or validity constraints beyond it, making the baseline 3 correct.

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 does say this retrieves a single service via GET /v1/services/{serviceId}, which pins down the resource and the lookup key. But the phrase 'Get service' essentially restates the tool name and title, and it gives no basis for choosing this over sibling reads like get_service_properties or get_connector.

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 or when-not-to-use guidance at all. The agent is not told the difference between fetching a service and fetching its properties, nor are any prerequisites (auth, tenant scope, permissions) mentioned.

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