Skip to main content
Glama
Sign In
Othos MCP

Othos MCP

Official
by othos-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

othos_ticket_get

Retrieve a specific ticket by its unique ID. Adjust the maximum summary length to control the detail of the returned information.

Instructions

Get one ticket by ID using the fixed chat template format.

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": {
      "ticketId": "<ticketId>"
    },
    "name": "othos_ticket_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticketIdYes
summaryMaxLengthNoMax summary length for ticket description. Default: 240.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are present, so the description must fully disclose behavior. It mentions a 'fixed chat template format' but does not explain what this format entails, nor does it confirm read-only status, auth requirements, or rate limits. This leaves significant ambiguity for a read operation.

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?

The description is a single sentence with no unnecessary words. The key purpose and distinguishing detail are front-loaded, making it easy to scan.

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 lack of annotations and output schema, the description is insufficient. It does not mention what the 'fixed chat template format' output looks like, whether summaryMaxLength truncates, or any error conditions. For a simple get tool, more context is needed for a complete understanding.

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?

Schema coverage is 50% (only summaryMaxLength has a description). The tool description adds no additional meaning for ticketId beyond what the name implies. For summaryMaxLength, it repeats the schema's constraint without adding context about its impact on the response. The description does not compensate for the missing schema description of ticketId.

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 action ('Get'), the resource ('one ticket'), and a distinguishing detail ('by ID using the fixed chat template format'). This effectively differentiates it from sibling tools like list or update.

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 lacks guidance on when to use this tool versus alternatives such as othos_ticket_list_by_column or othos_ticket_get_template. No when-not-to-use or exclusionary criteria are provided.

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