TiFlux MCP Server

Official

by tiflux

Overview Schema Source Related Servers Discussions Admin

JavaScript

Hybrid

search_client

Search clients in TiFlux by partial name match. Retrieve client details for ticket management and support tasks.

Instructions

Buscar clientes no TiFlux por nome

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": {
      "client_name": "<client_name>"
    },
    "name": "search_client"
  }
}

Input Schema

Name	Required	Description	Default
`client_name`	Yes	Nome do cliente a ser buscado (busca parcial)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.3.0Jun 11, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the search functionality without mentioning any behavioral traits such as idempotency, rate limits, or pagination. For a read-only tool, this is insufficient.

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?

The description is a single sentence that is front-loaded with the key information. Every word serves a purpose, making it highly concise and efficient.

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?

Despite the absence of an output schema, the description is fairly complete for a simple search tool with one parameter. It could mention that the output is a list of matching clients, but the tool name and context imply this. No major gaps.

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?

The schema description coverage is 100%, with the parameter 'client_name' already described as partial search. The tool description adds no additional meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the verb 'Buscar' (search), the resource 'clientes' (clients), and the context 'no TiFlux' (in TiFlux) with the criterion 'por nome' (by name). This distinguishes it from sibling search tools like search_user or search_stage.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool (to search clients by name), but does not explicitly mention when not to use it or provide alternatives. The context is clear enough for an agent to differentiate from sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.