Skip to main content
Glama

Babelii-Diofis Customer Support

Buka tiket ke staf

contact_support

Open a support ticket for staff, only after search_help did not solve the problem or the customer asks for a person. name is required; contact (phone or email) is optional. Returns a reference and, for anonymous callers, a one-time access_code: give both to the customer exactly as returned. Limited per caller; do not retry the same ticket.

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": {
      "name": "<name>",
      "subject": "<subject>",
      "message": "<message>"
    },
    "name": "contact_support"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
contactNo
messageYes
subjectYes
order_numberNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, non-idempotent), it discloses the return shape (a reference plus a one-time access_code for anonymous callers), an instruction to relay both to the customer verbatim, and a per-caller rate limit. These are real behavioral facts the annotations do not carry. It stops short of saying what happens on failure or what staff do with the ticket, so it is strong but not exhaustive.

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?

The trigger condition is front-loaded ahead of parameter notes and return handling, which is the right order, and every sentence carries information. The brief middle clause about name/contact is slightly noisy because it lists only two of five parameters, breaking the parallel structure.

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 non-destructive mutation with a rate limit and a sensitive return value, the description covers the trigger, the key parameter meaning, and how to handle the access_code. An output schema exists, so return format need not be spelled out, and the main remaining gap is the undocumented subject/message/order_number semantics.

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 description coverage is 0%, so the description carries the burden: it adds real meaning for contact ('phone or email') and flags name as required. However, subject, message, and order_number are never explained, and singling out 'name is required' while omitting that subject and message are also required is mildly misleading against the schema.

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 verb and resource ('Open a support ticket for staff') and explicitly distinguishes itself from search_help, the main sibling it could be confused with. Minor ambiguity remains in 'for staff' and there is no differentiation from siblings like ticket_status or discover_support, but an agent can tell what this tool does.

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

Usage Guidelines5/5

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

It gives an explicit precondition ('only after search_help did not solve the problem or the customer asks for a person') that names the alternative sibling and the condition selecting it. It also gives an anti-pattern ('do not retry the same ticket'), which is exactly the when-not guidance that prevents misuse.

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