Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Alive

alive
Read-onlyIdempotent

Checks IPEX API availability by calling its health endpoint, helping you confirm the service is reachable before making requests.

Instructions

Alive check route. IPEX API: GET /alive.

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": "alive"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the underlying HTTP endpoint, which signals a trivial side-effect-free probe. It does not say whether the call requires authentication or what a successful versus failing probe looks like, which is the main behavioral detail an agent would still need.

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

Conciseness5/5

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

Two short sentences, front-loaded with the purpose and followed by the endpoint reference. Nothing is padded or repeated.

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

Completeness4/5

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

For a zero-parameter, no-output-schema liveness probe, the definition supplies enough for correct invocation. The remaining gap is the return signal — what a healthy versus unhealthy response looks like — which the absent output schema leaves undocumented.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The endpoint note adds contextual meaning about what the call resolves to.

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

Purpose4/5

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

The description states a specific function — a liveness/health check — and names the exact upstream route (GET /alive), which makes it clearly distinct from the data-retrieval siblings that all fetch domain objects. It stops short of a full verb+resource phrasing, but 'Alive check route' is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is a reachability/health probe rather than a data call. There is no explicit statement of when to call it (e.g., before a batch of requests, to verify connectivity or credentials) and no mention of alternatives or when not to use it.

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