Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Search Services Fulltext

search_services_fulltext
Read-onlyIdempotent

Find IPEX service records with a full-text query, optionally filtered by service type or customer ID via the IPEX API.

Instructions

Service full text search. IPEX API: GET /v1/services/fulltext.

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

Input Schema

NameRequiredDescriptionDefault
typeNoQuery parameter 'type' of the IPEX API.
customerIdNoQuery parameter 'customerId' of the IPEX API.
fullTextSearchNoQuery parameter 'fullTextSearch' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. Beyond restating the HTTP endpoint, the description says nothing about matching behavior, case sensitivity, result caps, pagination, or ranking, which is what an agent actually needs to know about a full-text search.

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?

It is two short fragments with no filler, and the purpose statement is front-loaded. The endpoint line is marginal but cheap and does convey REST semantics, so it does not meaningfully hurt the definition.

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?

With three optional parameters, no output schema, and no required inputs, the description should explain at least what a call returns and what happens when all filters are omitted. It leaves return shape, result volume, and empty-query behavior entirely unspecified.

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%, and each parameter already carries a description, so the schema does the heavy lifting. The description adds no meaning about what fullTextSearch accepts (free text, fielded query, partial words) or what type and customerId filter, so it sits at the baseline for high-coverage schemas.

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 names the resource (services) and the operation (full text search), and it maps to a concrete endpoint, GET /v1/services/fulltext. However, it is a terse noun-phrase rather than a verb-led statement, and it does not distinguish this tool from lookalike siblings such as list_services or search_ruian.

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 guidance on when to choose this tool over list_services or the other search/list siblings, and no mention of prerequisites such as required scoping or when a plain list is preferable to a full-text query. The agent must infer usage from the name alone.

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