Skip to main content
Glama

Babelii-Diofis Customer Support

Kenali layanan pelanggan

discover_support
Read-onlyIdempotent

What customer service can and cannot do, the ticket rules, and whether this connection is anonymous or tied to an account.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description earns credit for disclosing something annotations cannot: that the response reveals whether the session is anonymous or account-bound, plus the ticket policy rules — both materially affect what the agent should do next.

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?

A single compact sentence with three clearly separated content areas and no filler. It loses a point only because it is an elliptical noun phrase with no main verb, and "the ticket rules" is vague enough that the reader cannot tell what rules are meant until they call the tool.

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?

With no parameters, an output schema to explain return values, and annotations covering the safety profile, the description only needs to say what knowledge it exposes — which it does across three distinct areas. The remaining gap is positional guidance (call this first, before contacting support), which is absent.

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 the baseline is 4. Nothing about parameters needs explaining, and the description correctly spends no words on input syntax.

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 enumerates the specific content the tool surfaces: support capabilities and limits, ticket rules, and the anonymity/account binding of the connection. That is concrete enough to separate it from contact_support or ticket_status, though it never states a verb ("returns", "describes") and the title is in Indonesian, so the purpose reads as a list of topics rather than a crisp action.

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, and no sibling is named. An agent must infer that this is an orientation call to make before contact_support or ticket_status; the description never says so, nor does it state any prerequisite or ordering.

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