Skip to main content
Glama
Sign In
TiFlux MCP Server

TiFlux MCP Server

Official
by tiflux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

list_internal_communications

Retrieve internal communications tied to a ticket number. Use offset and limit to paginate results.

Instructions

Listar comunicações internas existentes em um ticket específico

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": {
      "ticket_number": "<ticket_number>"
    },
    "name": "list_internal_communications"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticket_numberYesNúmero do ticket para listar as comunicações internas
offsetNoNúmero da página a ser retornada (padrão: 1)
limitNoNúmero de comunicações por página (padrão: 20, máximo: 200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention that the operation is read-only, any authorization requirements, pagination behavior, or side effects. The description is insufficient for an uninformed agent.

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 description is a single, short sentence with no redundancy. It is concise but could incorporate more useful information without sacrificing brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (list with pagination) and no output schema, the description is incomplete. It does not hint at the return format, ordering, or how pagination works. The presence of sibling tools like 'get_internal_communication' is not leveraged to clarify distinctions.

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 coverage is 100%, with each parameter described. The description adds no extra meaning beyond the schema (e.g., clarifying the return format or pagination behavior). Baseline 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 tool's purpose: listing internal communications for a specific ticket. The verb 'list' and resource 'internal communications' are specific, distinguishing it from siblings like 'get_internal_communication' and 'create_internal_communication'.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., 'get_internal_communication' for a single item). It lacks when-not-to-use or prerequisite information.

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

Deploy Server

Other Tools