Skip to main content
Glama

Babelii-Diofis Customer Support

Cari artikel bantuan

search_help
Read-onlyIdempotent

Retrieve approved help articles about how Babelii works (ordering, payment by link, tracking, limits, policies). Answer only from the returned references; if none fit, say so and offer a ticket. Never use them as a current price, balance or order status.

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": {
      "query": "<query>"
    },
    "name": "search_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuinely non-structured context: the corpus is limited to 'approved' articles, answers must be grounded strictly in returned references, and the results must never be presented as current price, balance, or order status.

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 sentences, no filler, and the highest-value information (what is retrieved and from which corpus) is front-loaded before the grounding and fallback constraints. Every clause carries a distinct instruction.

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?

An output schema exists, so return values need no explanation, and the tool is single-parameter and simple. Purpose, grounding policy, fallback, and the price/balance/status exclusion are all covered; only query-formation guidance is missing.

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

Parameters2/5

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

The single required parameter 'query' has 0% schema description coverage, so the description is the only place meaning could be added — and it says nothing about phrasing, language, keyword vs. natural-language input, or expected query scope. At low coverage with one documented-by-nothing parameter, this is a clear gap.

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?

"Retrieve approved help articles about how Babelii works" gives a specific verb (retrieve) and resource (approved help articles), and the parenthetical enumerates the covered topic areas (ordering, payment by link, tracking, limits, policies). It is clearly distinguishable from order_status/ticket_status via the closing restriction, though it never names a sibling outright.

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?

"Answer only from the returned references; if none fit, say so and offer a ticket" states the operating condition and the no-results fallback, which implicitly routes the agent to the support/ticket siblings. It stops short of enumerating when another sibling is the better first choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources