Skip to main content
Glama

Babelii-Diofis Customer Support

Status tiket

ticket_status
Read-onlyIdempotent

Status and staff replies of a ticket. Anonymous callers need the reference and the access_code from contact_support; a connected account needs only the reference of its own 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": {
      "reference": "<reference>"
    },
    "name": "ticket_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenceYes
access_codeNo

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?

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds important behavioral context about anonymous versus connected access and what the response contains, though it does not cover error behavior for invalid access codes.

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 are front-loaded with the result and then the access requirements. There is no redundant wording, and the most important scoping distinction is stated directly.

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 simple read-only ticket-status tool with an output schema and explicit safety annotations, the description covers the important auth prerequisites and returned content. Minor omissions such as exact status values or staff-reply pagination are acceptable given the output schema.

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?

With 0% schema description coverage, the description must explain the parameters, and it does: reference identifies the ticket, while access_code is required for anonymous callers and comes from contact_support. It does not specify formats or validation rules, but the conditional meaning of access_code is clearly conveyed.

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 resource and what is returned: the status and staff replies of a ticket. It is clear enough to distinguish this from unrelated support tools, though it does not explicitly contrast itself with order_status or other status-checking siblings.

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?

It gives clear usage conditions: anonymous callers need both reference and access_code from contact_support, while connected accounts need only the reference of their own ticket. It does not name explicit alternatives or when-not-to-use cases, but the auth-specific guidance is strong.

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